TWI672627B - Method, electronic device and non-transitory computer-readable storage medium of reducedsizeuser interfaces for battery management - Google Patents

Abstract

The invention discloses a device having a touch-sensitive display and a battery, which can determine the battery power of one of the batteries, and trigger a touch according to whether the battery power is at or below a first threshold value. Sense output and / or enter a low power mode. When in the low power mode, the device can respond to user input to produce an output that is different than when in a normal power mode. In some embodiments, when in the low power mode, the device can only display one of the indications of time and the device in a low power mode.

Description

Method, electronic device and non-transitory computer readable storage medium for reduced size user interface for battery management Cross-reference to related applications

The present application claims the "Reduced-size User Interfaces for Battery Management" application of "Reduced-size User Interfaces for Battery Management" on September 8, 2014, and "Reduced-size User Interfaces for Battery Management", filed on August 6, 2014. The priority of U.S. Provisional Application No. 62/034,103, the disclosure of which is incorporated herein in its entirety by reference.

This application is also related to U.S. Provisional Patent Application No. 62/033,819, entitled "Low Power Mode", filed on August 6, 2014, and entitled "Reduced-Size Interfaces for Managing" on September 2, 2014. U.S. Provisional Patent Application Serial No. 62/044,894, filed on Jul. 18, 2014, entitled,,,,,,,,,,,,,,,,,,,,,, The content is hereby incorporated by reference in its entirety.

The present invention is generally directed to computer user interfaces and, more particularly, to techniques for managing battery usage.

A reduced size personal electronic device, such as a device that is smaller than a cellular phone, can be used as a timer component and to provide other applications or functions. Providing timing functionality between the charging of the device's battery in the case where the personal electronic device can be the user's primary timer A relatively long period of time may be important. The timing functionality of the device can replace the importance of other applications or functions of the device.

A user interface that alerts the user to low battery levels and provides a user interface and method for extending the timing capabilities of the device is desirable, particularly for battery powered portable electronic devices in which battery storage is particularly beneficial.

In some embodiments, the method includes: at an electronic device having a touch-sensitive display, a battery, and a tactile mechanism: determining a battery level of the battery; causing a touch based on a determination that the battery level is at or below a first threshold The sensing mechanism emits a tactile output; receives data indicating the user input; determines whether the data has been received within a predetermined time interval after the tactile output; and based on the determination that the data has been received within the predetermined time interval, A battery alert is displayed on the touch-sensitive display.

In some embodiments, the electronic device comprises: a battery; a tactile mechanism; a touch sensitive display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory And configured to be executed by one or more processors, the one or more programs including instructions for determining a battery level of the battery; according to the battery level being at or below a first threshold Determining, causing the tactile mechanism to emit a tactile output; receiving data indicating the user input; determining whether the data has been received within a predetermined time interval after the tactile output; and receiving the data according to the pair of time intervals that have been received It is determined that a battery alert is displayed on the touch sensitive display.

In some embodiments, the non-transitory computer readable storage medium stores one or more programs including one or more of the electronic devices by having a touch sensitive display, a touch sensitive mechanism, and a battery The processor causes the electronic device to execute an instruction of: determining a battery power of the battery; causing the tactile mechanism to emit a tactile output according to the determination that the battery power is at or below the first threshold; receiving the indication user input Data; determine whether the data has been received within a predetermined time interval after the tactile output; A determination that the data has been received within a predetermined time interval displays a battery alert on the touch sensitive display.

In some embodiments, the electronic device includes: a battery; a tactile mechanism; a touch sensitive display; and a means for determining a battery level of the battery of the electronic device; for using the battery at or below the first threshold a member for causing the tactile sensation to emit a tactile output; a member for receiving a material indicating the user input; a member for determining whether the data has been received within a predetermined time interval after the tactile output is output; A means for displaying a battery alert on a touch-sensitive display based on a determination that data has been received within a predetermined time interval.

In some embodiments, the electronic device includes: a touch sensitive display unit; a battery unit; a haptic mechanism unit; and a processing unit coupled to the touch sensitive display unit, the battery unit, and the haptic mechanism unit, the processing unit The configuration is: determining the battery power of the battery unit; causing the tactile mechanism unit to emit a tactile output according to the determination that the battery power is at or below the first threshold; receiving the data indicating the user input; determining whether the battery is The data is received within a predetermined time interval after the tactile output; and the display of the battery alert on the touch-sensitive display unit is enabled based on the determination that the data has been received within the predetermined time interval.

In some embodiments, a method includes, at an electronic device having a touch-sensitive display, a battery, at least one hardware button, and a rotatable input mechanism, the electronic device configured to respond to being in a normal power mode Generating a first output at the input of the touch sensitive display, generating a second output in response to input at the at least one hardware button, and generating a third output in response to input at the rotatable input mechanism Determining the battery level of the battery; and determining whether the battery level is at or below the first threshold: entering the low power mode, the low power mode being characterized by responding to the touch sensitive display, at least one hardware button or A fourth output can be generated by rotating an input at any of the input mechanisms.

In some embodiments, the electronic device includes: one or more processors; a memory; a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by one or more processors Executing, the one or more programs include instructions for generating a first output in response to an input at the touch sensitive display when in the normal power mode, in response to the at least one hardware a second output is generated by the input at the button, and a third output is generated in response to the input at the rotatable input mechanism: determining a battery level of the battery; and determining whether the battery level is at or below the first threshold : Entering a low power mode characterized by generating a fourth output in response to an input at any of a touch sensitive display, at least one hardware button, or a rotatable input mechanism.

In some embodiments, the non-transitory computer readable storage medium stores one or more programs, including by a touch sensitive display, a battery, at least one hardware button, and a rotatable input mechanism When executed by one or more processors of the electronic device, the electronic device causes an instruction to: when in the normal power mode, generate a first output in response to the input at the touch-sensitive display, in response to the Inputting at least one hardware button to generate a second output, and generating a third output in response to input at the rotatable input mechanism: determining a battery level of the battery; and depending on whether the battery level is at or below the first Determination of the limit value: Entering a low power mode characterized by generating a fourth output in response to an input at any of a touch sensitive display, at least one hardware button, or a rotatable input mechanism.

In some embodiments, the electronic device comprises: a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; responsive to being at the touch sensitive display when the electronic device is in a normal power mode Inputting a first output, generating a second output in response to input at the at least one hardware button, and generating a third output in response to input at the rotatable input mechanism; for determining a battery a component of battery power; and means for entering a low power mode based on a determination that the battery power is at or below a first threshold, the low power mode being characterized by responding to the touch sensitive display A fourth output is generated by an input at any of the at least one hardware button or the rotatable input mechanism.

In some embodiments, the electronic device includes: a touch sensitive display unit; a battery unit; at least one hardware button unit; a rotatable input mechanism unit; and a processing unit coupled to the touch sensitive display unit, the battery unit The at least one hardware button unit and the rotatable input mechanism unit configured to: when in a normal power mode, generate a first output in response to an input at the touch-sensitive display unit Generating a second output in response to input at the at least one hardware button unit, and generating a third output in response to input at the rotatable input mechanism unit; determining a battery level of the battery unit; and A determination that the power is at or below the first threshold: entering a low power mode characterized by responding to a touch sensitive display unit, at least one hardware button unit, or a rotatable input mechanism unit The fourth output is generated by the input at one.

In some embodiments, the method includes: at an electronic device having a touch-sensitive display, a battery, and at least two input mechanisms: receiving a first data indicative of activation of the first input mechanism; receiving an indication indicating activation of the second input mechanism a second information, wherein the second data is received during a predetermined duration from the receipt of the first data; and in response to receiving the first data and the second data: determining that the battery reaches a first threshold The previous amount of remaining time, showing the amount of remaining time, showing a visual ancestry for invoking the low power mode, detecting the selection of the visual cues, and entering the low power mode in response to detecting the selection.

In some embodiments, the electronic device comprises: a touch sensitive display; a battery; at least two input mechanisms; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory And configured to be executed by one or more processors, the one or more programs comprising instructions for: receiving a first data indicative of activation of the first input mechanism; receiving an indication of the second input Second information on the initiation of the institution, in which Receiving the second data from a predetermined duration of time during which the first data is received; and in response to receiving the first data and the second data: determining a remaining amount of time before the battery reaches a first threshold value, The remaining amount of time is displayed, a visual cue for invoking the low power mode is displayed, the selection of the visual cue is detected, and in response to detecting the selection, the low power mode is entered.

In some embodiments, the non-transitory computer readable storage medium stores one or more programs, including one or more of the electronic devices by having a touch sensitive display, a battery, and at least two input mechanisms And executing, by the plurality of processors, an instruction for the electronic device to: receive first data indicating activation of the first input mechanism; receive second data indicating activation of the second input mechanism, wherein the first data is self-received Receiving the second data within a predetermined duration; and in response to receiving the first data and the second data: determining a remaining amount of time before the battery reaches a first threshold, displaying the remaining amount of time, A visual cue for invoking a low power mode is displayed, the selection of the visual cue is detected, and in response to detecting the selection, the low power mode is entered.

In some embodiments, the electronic device comprises: a touch sensitive display; a battery; at least two input mechanisms; means for receiving a first data indicative of activation of the first input mechanism; and means for receiving activation indicative of the second input mechanism a component of the second data, wherein the second data is received during a predetermined duration of time from receiving the first data; and in response to receiving the first data and the second data, determining that the amount of power in the battery reaches the first a means for displaying the remaining amount of time before the threshold, means for displaying the remaining amount of time, means for displaying a visual cues for calling the low power mode; means for detecting the selection of the visual cues, and The component that enters the low power mode in response to detecting the selection.

In some embodiments, the electronic device includes: a touch sensitive display unit; a battery unit; at least two input mechanism units; and a processing unit coupled to the touch sensitive display unit, the battery unit, and the at least two An input mechanism unit configured to: receive a first data indicating activation of the first input mechanism unit; receive an indication of the second input a second information of the activation of the institution unit, wherein the second data is received during a predetermined duration from the receipt of the first data; and in response to receiving the first data and the second data: determining the battery unit The amount of time remaining until the first threshold is reached, enabling the display of the remaining amount of time, enabling display of the visual cues for invoking the low power mode, detecting the selection of the visual cues, and responding to detecting the selection , enter the low power mode.

100‧‧‧Portable Multifunction Devices

102‧‧‧ memory

103‧‧‧Communication bus or signal line

104‧‧‧ wafer

106‧‧‧Input/Output (I/O) Subsystem

108‧‧‧RF circuit

110‧‧‧Optical circuit

111‧‧‧Speakers

112‧‧‧Touch-sensitive display system

113‧‧‧ microphone

116‧‧‧Input control device

118‧‧‧ peripheral device interface

120‧‧‧Processing unit/processor

122‧‧‧ memory controller

124‧‧‧External information

126‧‧‧ operating system

128‧‧‧Communication Module

130‧‧‧Contact/Motion Module

132‧‧‧Graphics module

133‧‧‧Tactile feedback module

134‧‧‧Text Input Module

135‧‧‧Global Positioning System (GPS) module

136‧‧‧Application

136-1‧‧‧Application

137‧‧‧Contact Module

138‧‧‧Phone module

139‧‧‧Video Conferencing Module

140‧‧‧Email client module

141‧‧‧ Instant Messaging (IM) Module

142‧‧‧Fitness Support Module

143‧‧‧ imaging module / camera module

144‧‧‧Image Management Module

145‧‧‧Video Player Module

146‧‧‧Music player module

147‧‧‧ browser module

148‧‧‧ calendar module

149‧‧‧Interface Tool Set Module

149-1‧‧‧Weather Interface Tool Set

149-2‧‧‧ Stock Interface Tool Set

149-3‧‧‧Calculator Interface Tool Set

149-4‧‧‧Alarm interface tool set

149-5‧‧‧ dictionary interface tool set

149-6‧‧‧User-created interface toolset

150‧‧‧Interface Tool Set Builder Module

151‧‧‧Search Module

152‧‧‧Video and music player module

153‧‧‧Note module

154‧‧‧Map module

155‧‧‧Connected video module

156‧‧‧ display controller

157‧‧‧Device/Global Internal Status

158‧‧‧ Optical Sensor Controller

159‧‧‧Intensity sensor controller

160‧‧‧Input controller

161‧‧‧Tactile feedback controller

162‧‧‧Power system

164‧‧‧Optical sensor

165‧‧‧Contact intensity sensor

166‧‧‧ proximity sensor

167‧‧‧Tactile output generator

168‧‧‧Accelerometer

170‧‧‧ Event Classifier

171‧‧‧ event monitor

172‧‧‧Click view judgment module

173‧‧‧Active event recognizer decision module

174‧‧‧ Event Dispatching Module

176‧‧‧data update program

177‧‧‧Object update program

178‧‧‧GUI update program

179‧‧‧Event data

180‧‧‧Event recognizer

182‧‧‧ event receiver

183‧‧‧Subsequent information

184‧‧‧ event comparator

186‧‧‧ Event definition

187-1‧‧‧Event 1

187-2‧‧‧Event 2

188‧‧‧Event Transfer Instructions

190‧‧‧Event Disposal Program

191‧‧‧Application View

192‧‧‧Application internal state

200‧‧‧User interface

202‧‧‧ fingers

203‧‧‧ stylus

204‧‧‧Home/Menu button

206‧‧‧Push button

208‧‧‧Volume adjustment button

210‧‧‧User Identification Module (SIM) card slot

212‧‧‧ headphone jack

300‧‧‧Devices

310‧‧‧Processing unit

320‧‧‧Communication bus

330‧‧‧Input/Output (I/O) interface

340‧‧‧ display

350‧‧‧ keyboard and / or mouse

355‧‧‧ Trackpad

357‧‧‧Tactile output generator

359‧‧‧ sensor

360‧‧‧Network communication interface

370‧‧‧ memory

380‧‧‧Drawing module

382‧‧‧ Presentation module

384‧‧‧Document Processing Module

386‧‧‧Website building module

388‧‧‧ disc production module

390‧‧‧Trial Balance Module

400‧‧‧User interface

402‧‧‧Signal strength indicator

404‧‧‧Time

405‧‧‧Blue indicator

406‧‧‧Battery status indicator

408‧‧‧System匣

410‧‧‧ indicator

414‧‧‧ indicator

416‧‧‧ icon

418‧‧‧ icon

420‧‧‧ icon

422‧‧‧ icon

424‧‧‧ icon

426‧‧‧ icon

428‧‧‧ icon

430‧‧‧ icon

432‧‧‧ icon

434‧‧‧ icon

436‧‧‧ icon

438‧‧‧ icon

440‧‧‧ icon

442‧‧‧ icon

444‧‧‧ icon

446‧‧‧ icon

450‧‧‧ display

451‧‧‧Touch-sensitive surface

452‧‧‧ main axis

453‧‧‧Main axis

460‧‧‧Contact

462‧‧‧Contact

468‧‧‧Contact

470‧‧‧Contact

500‧‧‧ devices

502‧‧‧ Subject

504‧‧‧Touch-sensitive display screen/touch screen

506‧‧‧ input mechanism

508‧‧‧ Input institution

512‧‧‧ busbar

514‧‧‧I/O section

516‧‧‧Computer Processor

518‧‧‧ memory

522‧‧‧Touch sensitive components

524‧‧‧Touch intensity sensitive components

530‧‧‧Communication unit

532‧‧‧GPS sensor

534‧‧‧Accelerometer

536‧‧‧Gyro

538‧‧‧motion sensor

540‧‧‧ Directional Sensor

606‧‧‧ button

610‧‧‧ screen

612‧‧‧Battery alert

614‧‧‧visible clues

616‧‧‧Low battery message

704‧‧‧ screen

706‧‧‧ Current time

708‧‧‧Instructions

710‧‧‧Information

712‧‧‧ screen

716‧‧‧Confirm visual cues

802‧‧‧ display release indicator

804‧‧‧ main screen

902‧‧‧ indication of threshold

904‧‧‧Indicative of remaining time

906‧‧‧ screen

1002‧‧‧ main screen

1104‧‧‧visible clues

1106‧‧‧ screen

1108‧‧‧visible clues

1202‧‧‧ screen

1204‧‧‧visible clues

1206‧‧‧Shutdown visual clues

1208‧‧‧visible clues

1210‧‧‧ Cancel visual clues

1212‧‧‧ screen

1214‧‧‧visible clues

1216‧‧‧visible clues

1300‧‧‧Processing procedures

1302‧‧‧ Block

1304‧‧‧ Block

1306‧‧‧ Block

1308‧‧‧ Block

1310‧‧‧ Block

1400‧‧‧Processing procedures

1402‧‧‧ Block

1404‧‧‧ Block

1500‧‧‧Processing procedures

1502‧‧‧ Block

1504‧‧‧ Block

1506‧‧‧ Block

1508‧‧‧ Block

1510‧‧‧ Block

1600‧‧‧Electronics

1602‧‧‧Touch sensitive display unit

1606‧‧‧ battery unit

1608‧‧‧Tactile mechanism unit

1610‧‧‧Processing unit

1612‧‧‧Battery power determination unit

1614‧‧‧Tactile mechanism control unit

1616‧‧‧ data receiving unit

1618‧‧‧Time determination unit

1620‧‧‧ display enable unit

1622‧‧‧Input detection unit

1624‧‧‧Output generating unit

1626‧‧‧Power mode unit

1650‧‧‧ hardware button unit

1652‧‧‧Rotatable input mechanism unit

1654‧‧‧Accelerometer unit

1656‧‧ gyro unit

1700‧‧‧Electronics

1702‧‧‧Touch sensitive display unit

1706‧‧‧ battery unit

1708‧‧‧ hardware button unit

1710‧‧‧ Rotatable input mechanism unit

1712‧‧‧Processing unit

1714‧‧‧Battery power determination unit

1716‧‧‧Power mode unit

1718‧‧‧Output generating unit

1720‧‧‧ display enable unit

1722‧‧‧Input detection unit

1724‧‧‧ Data receiving unit

1726‧‧‧Tactile mechanism control unit

1752‧‧‧Tactile mechanism unit

1754‧‧‧Accelerometer unit

1756‧‧ gyro unit

1800‧‧‧Electronics

1802‧‧‧Touch sensitive display unit

1806‧‧‧ battery unit

1808‧‧‧First Input Mechanism Unit

1810‧‧‧Second input mechanism unit

1812‧‧‧Processing unit

1814‧‧‧data receiving unit

1816‧‧‧Time determination unit

1818‧‧‧ display enable unit

1820‧‧‧Input detection unit

1822‧‧‧Power mode unit

1824‧‧‧Input detection unit

1826‧‧‧Output generating unit

1828‧‧‧Power mode unit

1830‧‧‧ data receiving unit

1850‧‧‧ hardware button unit

1852‧‧‧Rotatable input mechanism unit

1854‧‧‧Accelerometer unit

1856‧‧‧Gyroscope unit

1858‧‧‧Mechanical button unit

1860‧‧‧Capacitive button unit

For a better understanding of the various embodiments of the invention, reference should be made to

1A is a block diagram illustrating a portable multifunction device with a touch sensitive display, in accordance with some embodiments.

FIG. 1B is a block diagram illustrating an illustrative component for event handling in accordance with some embodiments.

2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

3 is a block diagram of an illustrative multi-function device having a display and a touch-sensitive surface, in accordance with some embodiments.

4A illustrates an exemplary user interface for an application function table on a portable multifunction device, in accordance with some embodiments.

4B illustrates an exemplary user interface of a multi-function device having a touch-sensitive surface separate from the display, in accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with some embodiments.

FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

Figure 6 illustrates an exemplary user interface for managing battery power.

Figure 7A illustrates an exemplary user interface for managing battery power.

Figure 7B illustrates an exemplary user interface for managing battery power.

Figure 7C illustrates an exemplary user interface for managing battery power.

Figure 8 illustrates an exemplary user interface for managing battery power.

Figure 9 illustrates an exemplary user interface for managing battery power.

FIG. 10A illustrates an exemplary user interface for managing battery power.

FIG. 10B illustrates an exemplary user interface for managing battery power.

Figure 11A illustrates an exemplary user interface for managing battery power.

Figure 11B illustrates an exemplary user interface for managing battery power.

Figure 12A illustrates an exemplary user interface for managing battery power.

Figure 12B illustrates an exemplary user interface for managing battery power.

13 is a flow chart illustrating an illustrative process for displaying a user interface for managing battery power.

14 is a flow chart illustrating an illustrative process for displaying a user interface for managing battery power.

15 is a flow chart illustrating an illustrative process for displaying a user interface for managing battery power.

16 is a functional block diagram of an electronic device configured to display a user interface, in accordance with some embodiments.

17 is a functional block diagram of an electronic device configured to display a user interface, in accordance with some embodiments.

18 is a functional block diagram of an electronic device configured to display a user interface, in accordance with some embodiments.

The following description sets forth exemplary methods, parameters, and the like. However, it should be understood that the description is not intended to limit the scope of the invention, but is instead provided as a description of exemplary embodiments.

There is a need to alert the user to the low battery level on the reduced size personal electronic device and the method and user interface for enabling battery life management. These methods and interfaces save electricity Force and increase the time between battery charging, and can also reduce the cognitive burden of the user and produce a more efficient human-machine interface.

In the following, FIGS. 1A-1B, 2, 3, 4A-4B, 5A-5B, and 16-18 provide a description of an exemplary device for performing techniques for managing battery power. 6 through 12B illustrate an exemplary user interface for managing battery power. 13 through 15 are flow diagrams illustrating methods of managing battery power in accordance with some embodiments. The user interface of Figures 6 through 12B is also used to illustrate the processing procedures described below, including the processing procedures of Figures 13 through 15.

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

The terminology used herein to describe the various embodiments are for the purpose of describing particular embodiments and are not intended to be limiting. The singular forms "a", "the", "the" and "the" are intended to include the plural. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It is to be understood that the terms "comprises" or "comprises" or "an" or "an" The existence or addition of integers, steps, operations, components, components, and/or groups thereof.

The term "if" may be interpreted to mean "at time" or "after" or "in response to judgment" or "in response to detection" depending on the context. Similarly, the phrase "if judged" or "if a condition or event is stated" may be interpreted as meaning "after judgment" or "in response to judgment" or "in detection" depending on the context. Stated condition Or after the event] or "Respond to the detection of [conditions or events stated]".

Embodiments of electronic devices, user interfaces of such devices, and associated processing programs for using such devices are described. In some embodiments, the device is a portable communication device such as a mobile phone that also contains other functions such as PDA and/or music player functionality. Illustrative embodiments of portable multifunction devices include, but are not limited to, Apple®, iPod Touch®, and iPad® devices from Cupertino, California. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (eg, touch screen displays and/or trackpads), are used as appropriate. It should also be understood that in some embodiments, the device is not a portable communication device but a desktop computer having a touch-sensitive surface (eg, a touch screen display and/or a touch pad).

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.

The device supports a variety of applications, such as one or more of the following: drawing applications, rendering applications, word processing applications, website building applications, disc creation applications, spreadsheet applications, gaming applications, Telephony applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital camera applications, web browsing applications, digital music player applications Program, and / or digital video player application.

The various applications executing on the device optionally use at least one common physical user interface device, such as a touch sensitive surface. The one or more functions of the touch-sensitive surface and the corresponding information displayed on the device are adjusted as appropriate and/or changed from one application to the next and/or within the respective application. In this manner, a common physical architecture of the device, such as a touch-sensitive surface, optionally supports a variety of applications with a user interface that is intuitive and transparent to the user.

Attention will now be directed to embodiments that are directed toward a portable device having a touch sensitive display. FIG. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112 in accordance with some embodiments. For convenience, touch-sensitive display 112 is sometimes referred to as a "touch screen" and is sometimes referred to as or as a touch-sensitive display system. The device 100 includes a memory 102 (which optionally includes one or more computer readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, and an audio circuit. 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external ports 124. Device 100 includes one or more optical sensors 164 as appropriate. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on device 100 (eg, a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more for generating a haptic output on device 100 (eg, generating a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). Tactile output generators 167. These components communicate via one or more communication busses or signal lines 103 as appropriate.

As used in this specification and the scope of the claims, the term "strength" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact (eg, finger contact) on a touch-sensitive surface, Or a substitute (agent) for the force or pressure of contact on a touch-sensitive surface. The intensity of the contact has a range of values including at least four different values, and more typically includes hundreds of different values (eg, at least 256). The strength of the contact is determined (or measured) using various methods and combinations of various sensors or sensors as appropriate. For example, one or more force sensors beneath or adjacent to the surface of the touch-sensitive surface are used as appropriate to measure the force at various points on the touch-sensitive surface. In some implementations, a combined (eg, weighted average) force measurement from a plurality of force sensors is used to determine the estimated force of the contact. Similarly, the pressure sensitive tip of the stylus is used as appropriate to determine the pressure of the stylus on the touch sensitive surface. Alternatively, depending on the situation, the size of the contact area detected on the touch-sensitive surface and/or its variation The capacitance of the touch-sensitive surface that is in close contact, and/or its variations, and/or the resistance of the touch-sensitive surface that is in close proximity and/or its variation is used as a substitute for the force or pressure of contact on the touch-sensitive surface. . In some implementations, the contact force or pressure substitute measurement is used directly to determine if the intensity threshold has been exceeded (eg, the intensity threshold described in units corresponding to the surrogate measurement). In some implementations, the contact force or pressure substitute measurement is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (eg, the intensity threshold is in pressure units) Measured pressure threshold). The use of the strength of the contact as a user input attribute allows the user to access additional device functionality on the reduced size device that may not be user accessible, and the reduced size device has a display for display Visual cues (eg, on a touch-sensitive display) and/or receiving a user's input (eg, via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or button).

As used in this specification and the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous location of the device, a component of the device (eg, a touch-sensitive surface) relative to another component of the device (eg, The physical displacement of the outer casing, or the displacement of the component detected by the user by its touch sensing relative to the center of mass of the device. For example, where a component of a device or device contacts a surface of a touch-sensitive user (eg, a finger, a palm, or other portion of the user's hand), the tactile output produced by the physical displacement will be used by the user. Interpreted as a tactile sensation that corresponds to a perceived change in a physical feature of a component of a device or device. For example, a user interprets the movement of a touch-sensitive surface (eg, a touch-sensitive display or a track pad) as a "click-down" or "up-click" of a physical actuator button. In some cases, even when the physical actuator button associated with the touch-sensitive surface that is physically pressed (eg, displaced) by the user's movement does not move, the user will still feel such as "downward" The tactile sensation of clicking or clicking up. As another example, even if the smoothness of the touch-sensitive surface does not change, the user still interprets or senses the movement of the touch-sensitive surface as a "roughness" of the touch-sensitive surface. degree". Although the user's such touch interpretation will be affected by the user's individualized sensory perception, there are many touch perceptions that are common to a larger portion of the user. Thus, unless otherwise stated, when the haptic output is described as corresponding to a particular sensory perception of the user (eg, "up click", "down click", "roughness"), the resulting tactile output corresponds to A physical shift of a device or component thereof that produces a sensory perception as described by a typical (or general) user.

It should be appreciated that device 100 is only one example of a portable multifunction device, and device 100 optionally has more or fewer components than is shown, combining two or more components as appropriate, or as different groups as appropriate. State or configuration component. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software (including one or more signal processing and/or special application integrated circuits).

Memory 102 can include one or more computer readable storage media. Computer readable storage media can be tangible and non-transitory. The memory 102 can include high speed random access memory and can also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid state memory devices. The memory controller 122 can control access to the memory 102 by other components of the device 100.

The peripheral device interface 118 can be used to couple the input and output peripheral devices of the device to the CPU 120 and the memory 102. One or more processors 120 execute or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions of device 100 and to process data. In some embodiments, peripheral device interface 118, CPU 120, and memory controller 122 can be implemented on a single wafer, such as wafer 104. In some other embodiments, it can be implemented on a separate wafer.

The RF (Radio Frequency) circuit 108 receives and transmits RF signals, which are also referred to as electromagnetic signals. The RF circuit 108 converts the electrical signal into an electromagnetic signal/self-electromagnetic signal to convert the electrical signal and communicates with the communication network and other communication devices via the electromagnetic signal. Circuitry circuitry 108 optionally includes well-known circuitry for performing such functions, including but not limited to antenna systems, RF reception Transmitter, one or more amplifiers, tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and the like. The RF circuit 108 is optionally connected by wireless communication with, for example, the Internet (also known as the World Wide Web (WWW)), the corporate intranet, and/or the wireless network (such as a cellular telephone network, a wireless local area network ( LAN and/or Metropolitan Area Network (MAN) network and other device communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short range communication. Wireless communication uses any of a number of communication standards, protocols, and technologies as appropriate, 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), Evolved Pure Data (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Broadband Code Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (for example, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and/or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for e-mail (eg, Internet messaging) Access Protocol (IMAP) and/or Post Office Protocol (POP)), instant messaging (eg, Extensible Messaging and Status Information Protocol (XMPP), Workflow Initiation Agreement for Instant Messaging and Status Information Utilization Extensions (SIMPLE), Instant Messaging and Status Information Service (IMPS), and/or Short Message Service (SMS), or any other Appropriate communication protocol (including the communication protocol from the filing date of this document not yet developed it).

The audio circuit 110, the speaker 111, and the 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 signal into a human audible sound wave. The audio circuit 110 also receives an electrical signal that is self-sound converted by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data Peripheral device interface 118 is used for processing. The audio data is retrieved from the memory 102 and/or the RF circuit 108 by the peripheral device interface 118 and/or the audio data is transmitted to the memory 102 and/or the RF circuit 108. In some embodiments, the audio circuit 110 also includes a headphone jack (eg, the headphone jack 212 of FIG. 2). The headphone jack provides an interface between the audio circuit 110 and the removable audio input/output peripheral device, such as an output only headset or with an output (eg, for one or both ears) Headphones) and input (for example, a microphone) for both headphones.

I/O subsystem 106 couples input/output peripheral devices (such as touch screen 112 and other input control devices 116) on device 100 to peripheral device interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, tactile feedback controller 161, and one or more inputs for other input or control devices. Controller 160. The one or more input controllers 160 receive electrical signals/transmit electrical signals from other input or control devices 116 to other input control devices 116. Another input control device 116 optionally includes physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, pointing wheels, and the like. In some alternative embodiments, the input controller 160 is coupled to any one of the following (or none): a keyboard, an infrared ray, a USB port, and an indicator device such as a mouse. One or more buttons (eg, button 208 of FIG. 2) (including up/down buttons for volume control of speaker 111 and/or microphone 113 as appropriate. One or more buttons include push buttons as appropriate (eg, Push button 206) of Figure 2.

Pressing a quick press of a button unlocks the touch screen 112 or initiates a process that uses gestures on the touch screen to unlock the device, such as the US patent filed on December 23, 2005. No. 11/322,549, "Unlocking a Device by Performing Gestures on an Unlock Image" (U.S. Patent No. 7,657,849), which is incorporated herein by reference in its entirety. A longer press of a push button (eg, push button 206) can turn the power of device 100 on or off. The user may be able to customize the functionality of one or more of the buttons. Touch screen 112 is used to implement virtual Or a screen button and one or more screen keypads.

The touch sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives and/or transmits electrical signals from the touch screen 112 to the touch screen 112. The touch screen 112 displays a visual output to the user. Visual output can include graphics, text, graphics, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to a user interface item.

Touch screen 112 has a touch-sensitive surface, a sensor or sensor set that accepts input from a user based on tactile and/or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and/or sets of instructions in the memory 102) detect contact (and any movement or interruption of contact) on the touch screen 112 and The detected contact is converted into an interaction with a user interface object (eg, one or more screen buttons, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display techniques may be used in other embodiments. Touch screen 112 and display controller 156 can detect any contact or any movement or interruption thereof using any of a number of touch sensing techniques now known or later developed, including but not limited to capacitors Sexual, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other components for determining one or more points of contact with touch screen 112. In an exemplary embodiment, a projected mutual capacitance sensing technique is used, such as the one found in Apple®'s iPhone® and iPod Touch® from Cupertino, California.

The touch sensitive display in some embodiments of the touch screen 112 can be similar to the multi-touch sensitive touch panel described in the following U.S. Patent and/or U.S. Patent Publication No. 2002/0015024 A1: 6, 323, 846 (Westerman et al.) 6,570,557 (Westerman et al.) and/or 6,677,932 (Westerman), each of which is hereby incorporated by reference. The full text is incorporated by reference. However, touch screen 112 displays visual output from device 100, while touch sensitive touch pads do not provide visual output.

The touch sensitive display of some embodiments of the touch screen 112 can be as described in the following application: (1) "Multipoint Touch Surface Controller", U.S. Patent Application Serial No. 11/381,313, filed on May 2, 2006. (2) US Patent Application No. 10/840,862, "Multipoint Touchscreen", filed on May 6, 2004; (3) US Patent Application Serial No. 10/903,964, filed on July 30, 2004, "Gestures For Touch" (4) "Gestures For Touch Sensitive Input Devices", U.S. Patent Application Serial No. 11/048,264, filed on Jan. 31, 2005; (5) U.S. Patent Application Serial No. "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices", No. 11/038,590; (6) "Virtual Input Device Placement On A Touch Screen User Interface", U.S. Patent Application Serial No. 11/228,758, filed on Sep. 16, 2005. (7) "Operation Of A Computer With A Touch Screen Interface", U.S. Patent Application Serial No. 11/228,700, filed on Sep. 16, 2005; /228,73 No. 7 "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard"; and (9) "Multi-Functional Hand-Held Device", U.S. Patent Application Serial No. 11/367,749, filed on March 3, 2006. All such applications are incorporated herein by reference in their entirety.

The touch screen 112 can have a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user can contact the touch screen 112 using any suitable item or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to function primarily with finger-based contacts and gestures based on finger contact and gestures attributable to the larger contact area of the finger on the touch screen and touch-based The input of the pen is less precise. In some embodiments, the device converts the rough input based on the finger into a precision indicator/cursor position or command to Used to perform the action the user wants.

In some embodiments, in addition to the touch screen, device 100 can include a touchpad (not shown) for activating or deactivating a particular function. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike a touchscreen, does not display a visual output. The touchpad can be a touch-sensitive surface that is separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes a power system 162 for powering various components. The power system 162 can include a power management system, one or more power sources (eg, batteries, alternating current (AC)), a recharging system, power fault detection circuitry, power converters or converters, power status indicators (eg, lighting) Diode (LED) and any other component associated with the generation, management, and distribution of power in a portable device.

Device 100 can also include one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 can include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) optoelectronic crystal. Optical sensor 164 receives ambient light projected through one or more lenses and converts the light into information representative of the image. In conjunction with the imaging module 143 (also referred to as a camera module), the optical sensor 164 can capture still images or video. In some embodiments, the optical sensor is located on the back of the device 100 opposite the touch screen display 112 on the front side of the device such that the touch screen display can be used as a seeker for static and/or video image acquisition. . In some embodiments, an optical sensor is located on the front side of the device such that when the user views other video conferencing participants on the touch screen display, the user's image is available for the video conference. In some embodiments, the position of the optical sensor 164 can be changed by a user (eg, by rotating a lens and sensor in the device housing) such that the single optical sensor 164 can be used in conjunction with a touch screen display Both video conferencing and static and/or video image acquisition.

Device 100 also includes one or more contact intensity sensors 165 as appropriate. Figure 1A shows A contact intensity sensor coupled to the intensity sensor controller 159 in the I/O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrodynamic sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensitive Surface or other intensity sensor (eg, a sensor for measuring the force (or pressure) of a contact on a touch-sensitive surface). The contact intensity sensor 165 receives contact intensity information (eg, a proxy for pressure information or pressure information) from the environment. In some embodiments, at least one contact intensity sensor is co-located or in proximity to the touch-sensitive surface (eg, touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back side of device 100 opposite touch screen display 112 on the front side of device 100.

Device 100 can also include one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to a peripheral device interface 118. Alternatively, proximity sensor 166 can be coupled to input controller 160 in I/O subsystem 106. The proximity sensor 166 can be implemented as described in the following U.S. Patent Application Serial No. 11/241,839, "Proximity Detector In Handheld Device"; No. 11/240,788 "Proximity Detector In Handheld Device"; No. 11/620,702 Using Ambient Light Sensor To Augment Proximity Sensor Output"; "Automated Response To And Sensing Of User Activity In Portable Devices", No. 11/586,862; and "Methods And Systems For Automatic Configuration Of Peripherals", No. 11/638,251, these applications The matter is hereby incorporated by reference in its entirety. In some embodiments, when the multifunction device is placed near the user's ear (eg, when the user is making a phone call), the proximity sensor is turned off and the touch screen 112 is disabled.

Device 100 also includes one or more haptic output generators 167 as appropriate. FIG. 1A shows a tactile output generator coupled to a haptic feedback controller 161 in I/O subsystem 106. The haptic output generator 167 optionally includes one or more electro-acoustic devices (such as speakers or other audio components), and/or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, Piezoelectric actuators, electrostatic actuators, or other tactile output Raw components (eg, components that convert electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives a haptic feedback generation command from haptic feedback module 133 and produces a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is co-located with or near the touch-sensitive surface (eg, touch-sensitive display system 112) and, as appropriate, by vertical (eg, entering/leaving device 100) The touch sensitive surface is moved to produce a tactile output either laterally or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the back side of device 100 opposite touch screen display 112 on the front side of device 100.

Device 100 can also include one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to a peripheral device interface 118. Alternatively, accelerometer 168 can be coupled to input controller 160 in I/O subsystem 106. The accelerometer 168 can be implemented as described in the following: US Patent Publication No. 20050190059 "Acceleration-based Theft Detection System for Portable Electronic Devices" and US Patent Publication No. 20060017692 "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer, both of which are incorporated herein by reference in their entirety. In some embodiments, the information is displayed on a touch screen display in a portrait view or a landscape view based on data analysis received from one or more accelerometers. In addition to accelerometer 168, device 100 includes, as appropriate, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining position and orientation with device 100 (eg, longitudinal or Horizontal) related information.

In some embodiments, the software components stored in the 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 an instruction set). 132. A text input module (or set of instructions) 134, a global positioning system (GPS) module (or set of instructions) 135, and an application (or set of instructions) 136. Moreover, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal states. 157, as shown in Figures 1A and 3. The device/global internal state 157 includes one or more of the following: active application state (indicating which applications (if any) are currently active); display status (indicating which applications, views, or other information occupy touch) The various states of the screen display 112; the sensor status (including information obtained from various sensors of the device and the input control device 116); and location information about the position and/or attitude of the device.

Operating system 126 (eg, Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes controls and management of general system tasks (eg, memory management, storage device control, Various software components and/or drivers for power management, etc., and facilitate communication between various hardware components and software components.

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 RF circuitry 108 and/or external port 124. External ports 124 (eg, universal serial bus (USB), FIREWIRE, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (eg, internet, wireless LAN, etc.). In some embodiments, the external turns are multi-pin (eg, 30-pin) connectors that are the same or similar and/or compatible with the 30-pin connectors used on iPod® (trademark of Apple Inc.) devices.

The contact/motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (eg, a trackpad or physical pointing wheel). The contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (eg, detecting a finger down event), determining the strength of the contact (eg, the force of contact) Or a substitute for pressure or contact force or pressure), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (eg, detecting one or more finger drag events), and determining if the contact has stopped (eg, , detecting finger up events or contact interruptions). Contact/motion module 130 receives contact data from a touch-sensitive surface. Judge The movement of the fixed contact point (which is represented by a series of contact data) optionally includes determining the rate (magnitude), velocity (magnitude and direction), and/or acceleration (variation in magnitude and/or direction) of the contact point. These operations are applied to a single contact (eg, one finger contact) or to multiple simultaneous contacts (eg, "multi-touch" / multiple finger contacts) as appropriate. In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touchpad.

In some embodiments, the contact/motion module 130 uses a set of one or more intensity thresholds to determine if the user has performed an operation (eg, to determine if the user has "clicked" the icon). In some embodiments, at least a subset of the intensity thresholds are determined based on the software parameters (eg, the intensity threshold is not determined by the activation threshold of the particular physical actuator, and it may not change the device 100) Adjusted in the case of physical hardware). For example, the mouse "click" threshold of the track pad or the touch screen display can be set to a predefined threshold of a larger range without changing the track pad or the touch screen display hardware. Any of the values. Additionally, in some implementations, the user of the device has software settings for adjusting one or more of the set of intensity thresholds (eg, by adjusting individual intensity thresholds, and/or by using system bits) Click the "Strength" parameter to adjust the multiple strength thresholds at a time.

The contact/motion module 130 detects the gesture input by the user as appropriate. Different gestures on the touch-sensitive surface have different contact patterns (eg, different motions, timings, and/or intensities of the detected contacts). Therefore, the gesture is detected by detecting a specific contact pattern as appropriate. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting the finger at the same location (or substantially the same location) as the finger down event (eg, at the location shown) Up (lift) the event. As another example, detecting a finger slip gesture on a touch-sensitive surface includes detecting a finger down event, followed by detecting one or more finger drag events, and then subsequently detecting the finger up (lifting up) )event.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including visual effects for changing the displayed graphics. A component (for example, brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphic" includes any object that can be displayed to a user, including but not limited to text, web pages, graphics (such as user interface objects including soft keys), digital video, video, animation. And similar.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is assigned to the corresponding code as appropriate. The graphic module 132 receives one or more code codes of the graphic to be displayed, and the coordinate data and other graphic property data (if necessary) from the application program or the like, and then generates the image data of the screen to output to the display controller 156.

The tactile feedback module 133 includes various software components for generating instructions for use by the tactile output generator 167 to generate tactile output at one or more locations on the device 100 in response to user interaction with the device 100. .

Text input module 134 (which may be a component of graphics module 132) is provided for use in various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input) Type a soft keyboard in the text.

The GPS module 135 determines the location of the device and provides this information for use by various applications (e.g., to the phone 138 for use in location-based dialing; to the camera 143 for image/video post-data; and for Provides location-based services such as the weather interface toolset, the local yellow page interface toolset, and the map/navigation interface toolset.

The application 136 can include the following modules (or sets of instructions), or a subset or superset thereof: a contact module 137 (sometimes referred to as an address book or contact list); a phone module 138; Conference module 139; ̇ email client module 140; ̇ instant messaging (IM) module 141; ̇ fitness support module 142; 摄影 camera module 143 for static and/or video images; ̇ image management module 144; ̇ video player module; ̇ music player module; ̇ browser module 147; ̇ calendar module 148; ̇ interface tool set module 149, which may include one or more of the following: weather interface tool set 149-1, stock interface tool set 149-2, calculator interface tool set 149-3 , the alarm clock interface tool set 149-4, the dictionary interface tool set 149-5, and other interface tool sets obtained by the user, and the user-created interface tool set 149-6; ̇ used to generate a user-created interface tool set 149 -6 interface tool set creator module 150; ̇ search module 151; ̇ video and music player module 152, which combines video player module 145 and music player module 146; ̇ note module 153; ̇ Map module 154; and/or ̇ Connect video module 155.

Examples of other applications 136 that can be stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, speech recognition. And voice overwriting.

In conjunction with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, and the text input module 134, the contact module 137 can be used to manage the address book or contact list (eg, stored in memory) The contact module 137 in the body 102 or the memory 370 In-app status 192), including: adding a name to the address book; deleting the name from the address book; associating a phone number, email address, physical address, or other information with the name; associating the image with the name Names are categorized and categorized; telephone numbers or email addresses are provided to initiate and/or facilitate communication via telephone 138, video conferencing module 139, email 140 or IM 141;

The telephone module 138 can be used in combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, and the text input module 134. Type a sequence of characters corresponding to the phone number, access one or more phone numbers in the contact module 137, modify the typed phone number, dial a separate phone number, make a conversation, and disconnect when the conversation is complete or hang up. As noted above, wireless communication can use any of a variety of communication standards, protocols, and techniques.

The RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact/motion module 130, and the graphic module are combined. 132. A text input module 134, a contact module 137, and a telephone module 138. The video conferencing module 139 includes a start, a process, and a termination between the user and one or more other participants according to a user instruction. Executable instructions for video conferencing.

In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, and the text input module 134, the email client module 140 is configured to respond to user commands. Executable instructions for creating, sending, receiving, and managing email. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or video images captured with the camera module 143.

In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, and the text input module 134, the instant messaging module 141 includes Used to type a sequence of characters corresponding to an instant message, modify a previously typed character, and transmit a separate instant message (eg, using a short message service (SMS) or multimedia message service (MMS) protocol for a phone-based instant message, or Executable instructions for using XMPP, SIMPLE, or IMPS for Internet-based instant messaging, receiving instant messages, and viewing incoming instant messages. In some embodiments, the transmitted and/or received instant messages may include graphics, photos, audio files, video files, and/or other additional files supported in MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (eg, messages sent using SMS or MMS) and Internet-based messages (eg, messages sent using XMPP, SIMPLE, or IMPS). .

The RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module are combined. The fitness support module 142 includes a fitness plan (eg, having time, distance, and/or calorie burning targets), communicating with a fitness sensor (sports device), receiving fitness sensor data, and calibrating for monitoring fitness. Sensors, executable instructions for fitness selection and playback of music, and display, storage and transmission of fitness data.

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

In combination with the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, the text input module 134, and the camera module 143, the image management module 144 includes configuration (eg, editing). Or otherwise manipulate, mark, delete, render (eg, in digital slides or albums) and executable instructions to store static and/or video images.

In combination with RF circuit 108, touch screen 112, display controller 156, contact/motion mode The group 130, the graphic module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving and displaying the webpage or parts thereof, and Link to additional files and other files on the web page.

In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, the text input module 134, the email client module 140, and the browser module 147, the calendar The module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and associated with the calendar (eg, calendar entries, proxy event listings, etc.) in accordance with user instructions.

In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the interface tool set module 149 is user-accessible. Download and use micro-apps (for example, weather interface tool set 149-1, stock interface tool set 149-2, calculator interface tool set 149-3, alarm interface tool set 149-4, and dictionary interface tool set 149-5 Or a micro-app created by the user (for example, user-created interface tool set 149-6). In some embodiments, the interface toolset includes HTML (Hypertext Markup Language) files, CSS (Cascading Forms) files, and JavaScript files. In some embodiments, the interface toolset includes XML (Extensible Markup Language) files and JavaScript files (eg, the Yahoo! Interface Toolkit).

In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the interface tool set builder module 150 can be used. It is used to create an interface tool set (for example, to turn a part specified by the user of a web page into an interface tool set).

In combination with the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, and the text input module 134, the search module 151 includes a search for matching one or the other in the memory 102 according to a user command. Executable instructions for text, music, sound, video, video, and/or other files of multiple search criteria (eg, one or more user-specified search items).

The video and music player module 152 includes a touch screen 112, a display controller 156, a contact/motion module 130, a graphics module 132, an audio circuit 110, a speaker 111, an RF circuit 108, and a browser module 147. Allowing a user to download and play executable instructions of recorded music and other sound files (such as MP3 or AAC files) stored in one or more file formats, and to display, render or otherwise play video (eg, Executable instructions on touch screen 112 or on an external display connected via external port 124. In some embodiments, device 100 optionally includes functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

In combination with the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, and the text input module 134, the note module 153 includes a list of events for creating and managing notes and agent events according to user instructions. Executable instructions for and the like.

The map module 154 is available in combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, the text input module 134, the GPS module 135, and the browser module 147. Receiving, displaying, modifying and storing maps and information associated with maps in accordance with user instructions (eg, driving directions; data on storage and other points of interest at or near specific locations; and other location-based information) ).

In combination with the touch screen 112, the display controller 156, the contact/motion module 130, the graphic module 132, the audio circuit 110, the speaker 111, the RF circuit 108, the text input module 134, the email client module 140, and browsing The module 147 includes a video module 155 that allows the user to access, browse, receive (eg, by streaming and/or downloading), play (eg, on a touch screen or via an external port 124). An external display connected to) an instruction to send an email with a link to a particular connected video and otherwise manage the connected video of one or more file formats, such as H.264. In some embodiments, the instant messaging module 141, rather than the email client module 140, is used to send a link to a particular connected video. An additional description of the connected video application can be found in the following: US Provisional Patent Application No. 60/936,562, "Portable", filed on June 20, 2007 "Multiple Device Device, Method, and Graphical User Interface for Playing Online Videos", and "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", which is filed on December 31, 2007. The content of the application is hereby incorporated by reference in its entirety.

Each of the above identified modules and applications corresponds to a method for performing one or more of the functions described above and described in the present application (eg, computer implementation methods and other information processing described herein) Method) An executable instruction set. Such modules (e.g., instruction sets) need not be implemented as separate software programs, programs, or modules, and thus, in various embodiments, various subsets of such modules may be combined or otherwise reconfigured. For example, the video player module can be combined with the music player module into a single module (eg, video and music player module 152, FIG. 1A). In some embodiments, memory 102 can store a subset of the modules and data structures identified above. In addition, the memory 102 can store additional modules and data structures not described above.

In some embodiments, device 100 is a device that exclusively performs the operation of a predefined set of functions on a device via a touch screen and/or trackpad. By using a touch screen and/or trackpad as the primary input control device for operation of device 100, physical input control devices (such as push buttons, dials, and the like) on device 100 can be reduced. number.

The predefined set of functions that are exclusively performed via the touchscreen and/or trackpad optionally include navigation between user interfaces. In some embodiments, the touchpad navigates device 100 from any user interface displayed on device 100 to a main menu, a home menu, or a root menu when touched by a user. In these embodiments, the "function table button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

FIG. 1B is a diagram illustrating an exemplary component for event handling in accordance with some embodiments. Block diagram. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event classifier 170 (eg, in operating system 126) and respective application programs 136-1 (eg, the aforementioned applications 137-151) , 155, 380 to 390).

The event classifier 170 receives the event information and determines which of the application view 191 of the application 136-1 and the application 136-1 is transmitted. 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 a current application view displayed on the touch-sensitive display 112 while the application is active or in execution. In some embodiments, event classifier 170 uses device/global internal state 157 to determine which application or applications are currently active, and event classifier 170 uses application internal state 192 to determine which applications to transmit event information to. View 191.

In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, indicating that the information being displayed or prepared by the application 136 -1 displays user interface status information for enabling the user to return to the status of the previous state or view of the application 136-1 and the redo/redo queue of the aforementioned actions taken by the user.

Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). The peripheral device interface 118 transmits information it receives from the I/O subsystem 106 or a sensor such as the proximity sensor 166, the accelerometer 168, and/or the microphone 113 (via the audio circuit 110). Information received by peripheral device interface 118 from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends a request to peripheral device interface 118 at predetermined time intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there is a significant event (eg, receiving an input above a predetermined noise threshold and/or exceeding a predetermined duration).

In some embodiments, event classifier 170 also includes a hit view decision module 172 and/or an active event recognizer decision module 173.

The click view decision module 172 provides a software program for determining where a sub-event occurs within one or more views when the touch-sensitive display 112 displays more than one view. The view consists of controls and other components that the user can see on the display.

Another aspect of the user interface associated with an application is a collection of views (sometimes referred to herein as an application view or a user interface window) in which information is displayed and touch-based gestures occur. The application view that detects the touch (of the respective application) may correspond to the stylized hierarchy within the stylized or view hierarchy of the application. For example, the lowest level view of the detected touch may be referred to as a click view, and the set of events identified as being properly input may be determined based, at least in part, on a click view of the initial touch that initiated the touch based gesture.

The click view decision module 172 receives information about sub-events based on touch gestures. When the application has multiple views organized in a hierarchy, the click view decision module 172 identifies a click view as the lowest view of the sub-events in the hierarchy. In most cases, the click view is the lowest level view in which the starting sub-event occurs (eg, the first sub-event in the sequence of sub-events that form an event or potential event). Once the click view decision module 172 identifies the click view, the click view typically receives all of the sub-events for the same touch or input source, so it is identified as a click view.

The active event recognizer decision module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer decision module 173 determines that only the click view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer decision module 173 determines that all views of the physical location including the sub-events are views of the active participation, and thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely limited to the area associated with a particular view, the higher view in the hierarchy will remain as the active participation view.

The event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In an embodiment including the active event recognizer decision module 173, the event dispatcher module 174 transmits event information to the event recognizer determined by the active event recognizer decision module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue, which is retrieved by the respective event receiver 182.

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, the application 136-1 includes an event classifier 170. In other embodiments, event classifier 170 is a stand-alone module or part of another module (such as contact/motion module 130) stored in memory 102.

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes separate views of the user interface for handling the application. An instruction for a touch event that occurs within. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the respective application views 191 include a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface set (not shown) or application 136-1 from which the method of inheritance and other properties are higher. Hierarchical objects. In some embodiments, the individual event handler 190 includes one or more of the following: a data update program 176, an object update program 177, a GUI update program 178, and/or event data 179 received from the event classifier 170. . The event handler 190 can utilize the data update program 176, the object update program 177, or the GUI update program 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more individual event handlers 190. Also, in some embodiments, one or more of the data update program 176, the object update program 177, and the GUI update program 178 are included in the respective application views 191.

The individual event recognizer 180 receives event information (e.g., event material 179) from the event classifier 170 and identifies the event from the event information. Event recognizer 180 includes event receiver 182 And event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of the following: post-data 183 and event transfer instructions 188 (which may include sub-event transfer instructions).

Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events (eg, touch or touch movement). Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When a sub-event relates to a touch motion, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes rotation of the device from one orientation to another (eg, from portrait orientation to landscape orientation, or vice versa), and the event information includes a current orientation of the device (also referred to as device pose) Corresponding information.

The event comparator 184 compares the event information with a predefined event or sub-event definition and, based on the comparison, determines the status of the event or sub-event or the decision or update event or sub-event. In some embodiments, event comparator 184 includes an event definition 186. Event definition 186 contains definitions of events such as event 1 (187-1), event 2 (187-2), and other events (eg, a sequence of predefined sub-events). In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, event 1 (187-1) is defined as a double tap on the displayed object. Double tapping, for example, includes a first touch (touch start) on the displayed item for a predetermined predetermined period, a first lift (a touch end) that continues for a predetermined period, and a second touch on the displayed object for a predetermined period of time ( Touch start) and continue the second lift of the predetermined phase (touch end). In another example, event 2 (187-2) is defined as a drag on the displayed object. Dragging, for example, touches (or contacts) on the displayed object for a predetermined period of time, movement of the touch across the touch-sensitive display 112, and lifting of the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a click test to determine Which user interface object is associated with a sub-event. For example, in an application view in which three user interface objects are displayed on the touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparator 184 performs a click test to determine three Which of the user interface objects is associated with the touch (sub-event). If each of the displayed items is associated with a respective event handler 190, the event comparator uses the results of the click test to determine which event handler 190 should be launched. For example, event comparator 184 selects an event handler associated with the sub-event and the item that triggered the click test.

In some embodiments, the definition of the respective event (187) also includes delaying the transmission of event information until the determined sub-event sequence corresponds to a delayed action following the event type of the event recognizer.

When the individual event recognizer 180 determines that a series of sub-events do not match any of the event definitions 186, the respective event recognizer 180 types an event impossible, event failure, or event end state, after which the touch-based gesture is ignored. Subsequent sub-events. In this case, the other event recognizers (if any) in the click view remain active to continue tracking and processing the ongoing touch-based gesture sub-events.

In some embodiments, the individual event recognizer 180 includes post-data 183 having configurable properties, flags, and/or manifests indicating how the event delivery system should perform sub-event delivery to the actively participating event recognizer. In some embodiments, the post-data 183 includes configurable properties, flags, and/or manifests that indicate how the event recognizers can interact, or can interact with each other. In some embodiments, the post material 183 includes configurable properties, flags, and/or manifests indicating whether sub-events are transmitted to different levels in the view or stylized hierarchy.

In some embodiments, the individual event recognizer 180 initiates an event handler 190 associated with the event upon recognizing one or more specific sub-events of the event. In some embodiments, the individual event recognizer 180 transmits event information associated with the event to the event handler 190. The launch event handler 190 is different from the send (and postpone) sub-event to the respective click view. In some embodiments, event recognizer 180 throws back associated with the identified event The flag is associated with the event handler 190 associated with the flag to capture the flag and execute a predefined handler.

In some embodiments, event transfer instructions 188 include sub-event transfer instructions that communicate event information about sub-events without launching an event handler. The fact is that the sub-event delivery command transmits event information to an event handler associated with a series of sub-events or to an active participation view. An event handler associated with a series of sub-events or having an active participation view receives event information and executes a predetermined handler.

In some embodiments, the data update program 176 generates and updates the data for use in the application 136-1. For example, the data update program 176 updates the phone number used in the contact module 137 or stores the video file for use in the video player module. In some embodiments, the item update program 177 generates and updates objects for use in the application 136-1. For example, the object update program 177 generates a new user interface object or updates the location of the user interface object. The GUI update program 178 updates the GUI. For example, the GUI update program 178 is ready to display information and send it to the graphics module 132 for display on the touch-sensitive display.

In some embodiments, event handler 190 includes or has access to data update program 176, object update program 177, and GUI update program 178. In some embodiments, the data update program 176, the object update program 177, and the GUI update program 178 are included in a single module of the respective application 136-1 or the application view 191. In other embodiments, it is included in two or more software modules.

It will be appreciated that the foregoing discussion of event handling for user touch on a touch sensitive display is also applicable to other forms of user input for operating the multifunction device 100 with input devices, not all such user inputs are Start on the touch screen. For example, the mouse movement and the mouse button pressing as appropriate (which may be pressed or held by a single or multiple keyboards, contact movement (such as light touch, drag, scroll, etc. on the touch panel), touch Pen input, device movement, verbal command, detected eye movement, raw The statistic input; and/or any combination thereof is used as input to a sub-event corresponding to the event defining the event to be identified.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen displays one or more graphics within the user interface (UI) 200 as appropriate. In this embodiment and other embodiments described below, the user can use, for example, one or more fingers 202 (not drawn to scale in the drawings) or one or more styluses 203 (pattern) It is not drawn to scale) to make a gesture on the graphic and select one or more of the graphics. In some embodiments, the selection of one or more graphics occurs when the user interrupts contact with one or more graphics. In some embodiments, the gesture includes one or more taps, one or more slips (from left to right, from right to left, up and/or down) of the finger that has touched the device 100, as appropriate, and / or scroll (from right to left, left to right, up and / or down). In some implementations or situations, unintentional contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, the swipe gesture that swept the application icon does not select the corresponding application as appropriate.

Device 100 may also include one or more physical buttons, such as a "home page" or menu button 204. As previously described, menu button 204 can be used to navigate to any application 136 in the set of applications executable on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key displayed in a GUI on the touch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering on/off the device and a lock device, a volume adjustment button 208, and a subscriber identity module (SIM) card. The slot 210, the earphone jack 212, and the plug/charge external port 124. Push button 206 is optionally used to turn the power of the device on/off by pressing the button and holding the button in a pressed state for a predetermined time interval; for pressing the button and before passing the predefined time interval Release the button to lock the device; and/or to unlock the device or initiate an unlock handler. In an alternative embodiment, device 100 also accepts a verbal input for activating or deactivating some functions via microphone 113. In. The device 100 also includes one or more contact intensity sensors 165 for detecting the intensity of the contact on the touch screen 112, and/or one or both for generating a tactile output for the user of the device 100. A plurality of haptic output generators 167.

3 is a block diagram of an illustrative multi-function device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop, tablet, multimedia player device, navigation device, teaching device (such as a children's learning toy), gaming system, or control device (eg, home control) Or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication busses 320 for interconnecting such components. Communication bus 320 includes, as appropriate, circuitry for interconnecting and controlling communications between system components (sometimes referred to as a chipset). Device 300 includes an input/output (I/O) interface 330 that includes display 340, which is typically a touch screen display. The I/O interface 330 also includes a keyboard and/or mouse (or other indicator device) 350 and a trackpad 355, as appropriate, for generating a tactile output 357 on the device 300 (eg, similar to Referring to the haptic output generator 167) depicted in FIG. 1A, a sensor 359 (eg, optical, acceleration, proximity, touch sensitive, and/or similar to the contact intensity sensor 165 described above with respect to FIG. 1A) Contact strength sensor). Memory 370 includes high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally non-volatile memory, such as one or more disk storage devices, optical disk storage Devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, the memory 370 stores programs, modules, and data structures, or subsets thereof, of programs, modules, and data structures stored in the memory 102 of the portable multifunction device 100 (FIG. 1A). . In addition, the memory 370 stores additional programs, modules, and data structures that are not present in the memory 102 of the portable multifunction device 100 as appropriate. For example, the memory 370 of the device 300 stores the graphics module as appropriate. 380, the presentation module 382, the document processing module 384, the website creation module 386, the disc production module 388, and/or the trial balance module 390, and the memory 102 of the portable multifunction device 100 (FIG. 1A) These modules are not stored as appropriate.

Each of the above identified components in Figure 3 can be stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The modules or programs (eg, sets of instructions) identified above need not be implemented as separate software programs, programs, or modules, and thus, in various embodiments, various components of such modules are combined or otherwise reconfigured. set. In some embodiments, memory 370 can store a subset of the modules and data structures identified above. In addition, the memory 370 can store additional modules and data structures not described above.

Attention will now be directed to embodiments that can be implemented on a user interface, such as on a portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for an application function table on portable multifunction device 100, in accordance with some embodiments. A similar user interface can be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: 信号 signal strength indicator 402 for wireless communication (such as cellular and Wi-Fi signals); ̇ time 404; indigo Bud indicator 405; ̇Battery status indicator 406; 匣 System 408 with graphical representations for frequently used applications, such icons: o for icon 416 of telephone module 138, labeled " "Phone", which optionally includes an indicator 414 of the number of missed calls or voicemail messages; o is used for icon 418 of the email client module 140, labeled "mail", An indicator 410 including the number of unread emails, as appropriate; o for the icon 420 of the browser module 147, labeled "Browser"; and o for the video and music player module 152 (which is also An illustration 422, referred to as an iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and 图示 for other applications, such as: o for icon 424 of IM module 141, labeled For the "message"; o is used for the icon 426 of the calendar module 148, labeled "calendar"; o for the image management module 144 icon 428, labeled "photo"; o for the camera module Figure 430 of 143, labeled "Camera"; o for icon 432 of the connected video module 155, labeled "Connected Video"; o for icon 434 of the Stock Interface Tool Set 149-2, labeled For the "stock"; o for the map module 154 icon 436, marked as "map"; o for the weather interface tool set 149-1 icon 438, labeled "weather"; o for the alarm interface tool The icon 440 of the set 149-4 is labeled "alarm clock"; o is used for the graphic 442 of the fitness support module 142, labeled "健"Support"; o is used for icon 444 of note module 153, labeled "notes"; and o is used to set an application or module icon 446, labeled "Settings", which is provided for device 100 and Access to the settings of its various applications 136.

It should be noted that the pictorial representations illustrated in Figure 4A are merely illustrative. For example, the icon 422 for the video and music player module 152 can be optionally labeled "Music" or "Music Player." Other tags are used as appropriate for various application icons. In some embodiments, the indicia for the respective application icons includes the names of the applications corresponding to the respective application icons. In some embodiments, the indicia for a particular application icon is different from the name of the application corresponding to that particular application icon.

4B illustrates a device (eg, a diagram) having a touch-sensitive surface 451 (eg, the tablet or trackpad 355 of FIG. 3) that is separate from display 450 (eg, touch screen display 112). An exemplary user interface on device 300 of 3. Device 300 also includes one or more contact intensity sensors (eg, one or more of sensors 357) for detecting the intensity of contact on touch-sensitive surface 451, as appropriate, and/or for One or more haptic output generators 359 that generate a tactile output for a user of device 300.

Although some of the following examples (in which the touch-sensitive surface and display are combined) will be given with reference to the inputs on the touch screen display 112, in some embodiments, the device detects a touch-sensitive surface that is separate from the display. Input, as shown in Figure 4B. In some embodiments, the touch-sensitive surface (eg, touch-sensitive surface 451 in FIG. 4B) has a major axis (eg, main axis 452 in FIG. 4B) that corresponds to a display (eg, display 450) The upper main axis (for example, the main axis 453 in Figure 4B). In accordance with such embodiments, the device detects contact with the touch-sensitive surface 451 at locations corresponding to respective locations on the display (eg, contact 460 and contact 462 in FIG. 4B) (eg, in FIG. 4B, Contact 460 corresponds to contact 468 and contact 462 corresponds to contact 470). In this manner, the user input (eg, contacts 460 and 462, and movement thereof) detected by the device on a touch-sensitive surface (eg, touch-sensitive surface 451 in FIG. 4B) is used by the device to The user interface on the display of the multi-function device (e.g., display 450 in Figure 4B) is manipulated when the touch-sensitive surface is separated from the display. It should be understood that similar methods are used as appropriate for other user interfaces described herein. .

Moreover, while the following examples are given primarily with reference to finger input (eg, finger contact, finger tap gesture, finger slip gesture), it should be understood that in some embodiments, one or more finger inputs are from another input device. The input is replaced (for example, based on mouse input or stylus input). For example, the mouse clicks (eg, instead of touching) as appropriate, followed by the movement of the cursor along the path of the slip (eg, instead of the movement of the contact) to replace the slip gesture. As another example, when the cursor is over the location of the tap gesture, the mouse click is optionally invoked (eg, instead of detecting the contact, followed by stopping detecting the contact) to replace the tap gesture. Similarly, when multiple user inputs are detected at the same time, it should be understood that Use multiple computer mice at the same time, or use the mouse and finger contact as appropriate.

FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, the device can include some or all of the features described with respect to devices 100 and 300 (eg, FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504 (hereinafter referred to as touch screen 504). Alternatively, or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch sensitive surface) can have one or more intensity sensors for detecting the strength of an applied contact (eg, touch) . One or more intensity sensors of the touch screen 504 (or touch sensitive surface) can provide output data indicative of touch intensity. The user interface of device 500 can respond to the touch based on the intensity of the touch, meaning that different intensity touches can involve different user interface operations on device 500.

A technique for detecting and processing touch intensity can be found, for example, in the following related application: "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", which was filed on May 8, 2013. International Patent Application No. PCT/US2013/040061, and International Patent Application No. PCT/ entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", filed on November 11, 2013 US 2013/069483, each of which is incorporated herein by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may permit device 500 to be attached to, for example, a hat, eyeglasses, earrings, necklace, shirt, jacket, bracelet, strap, chain, pants, belt, shoe, wallet, backpack, and the like. Such attachment mechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts an exemplary personal electronic device 500. In some embodiments, device 500 Some or all of the components described with respect to FIG. 1A, FIG. 1B, and FIG. 3 may be included. Device 500 has a busbar 512 that operatively couples I/O section 514 to one or more computer processors 516 and memory 518. I/O section 514 can be coupled to display 504, which can have touch sensitive component 522 and optionally touch intensity sensitive component 524. Additionally, I/O section 514 can be coupled to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular and/or other wireless communication technologies. Device 500 can include input mechanisms 506 and/or 508. For example, input mechanism 506 can be a rotatable input device or a pushable and rotatable input device. In some examples, input mechanism 508 can be a button.

In some examples, input mechanism 508 can be a microphone. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, direction sensor 540 (eg, compass), gyroscope 536, motion sensor 538, and/or combinations thereof, All are operatively connected to I/O section 514.

The memory 518 of the personal electronic device 500 can be a non-transitory computer readable storage medium for storing computer executable instructions that, when executed by one or more computer processors 516, for example, can cause the computer The processor performs the techniques described above, including processing procedures 1300 through 1500 (Figs. 13-15). The computer executable instructions can also be stored and/or transferred to any non-transitory computer readable storage medium for use in conjunction with or in connection with an instruction execution system, apparatus, or device (such as a computer-based system, a processor-containing system, or a self-executable The system, device, or device is used by other systems that extract instructions and execute instructions. For the purposes of this document, a "non-transitory computer readable storage medium" can be any medium that can tangibly contain or store computer-executable instructions for use with or in connection with an instruction execution system, apparatus, or device. Non-transitory computer readable storage media may include, but are not limited to, magnetic, optical, and/or semiconductor storage. Examples of such storage include magnetic disks, CD-ROM based on CD, DVD or Blu-ray technology, and persistent solid state memories such as flash memory, solid state disk drives and the like. Personal electronic device 500 is not limited to the components and configurations of Figure 5B, but may include multiple configurations Other or additional components in .

As used herein, the term "visual cues" refers to a graphical user interface object that can be displayed by a user on a display screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example, images (eg, icons), buttons, and text (eg, hyperlinks) may each constitute a visual cue.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of the user interface that the user is interacting with. In some implementations including cursors or other position markers, the cursor acts as a "focus selector" such that when on a touch-sensitive surface (eg, touchpad 355 in Figure 3 or touch-sensitive surface 451 in Figure 4B) When an input is detected (eg, a press input) and the cursor is over a particular user interface component (eg, button, window, slider, or other user interface component), the particular user is adjusted based on the detected input Interface component. Some of the touch screen displays (eg, touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enable direct interaction with user interface elements on a touch screen display In practice, the touch detected on the touch screen acts as a "focus selector" to enable specific user interface components (eg, buttons, windows, sliders, or other users) on the touch screen display. When an input is detected at the location of the interface component (eg, by a press input of a contact), a particular user interface component is adjusted based on the detected input. In some implementations, where there is no corresponding cursor movement or contact movement on the touch screen display (eg, by using a tab or arrow keys to move the focus from one button to another), The focus moves from one area of the user interface to another area of the user interface; in such implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the particular form in which the focus selector is employed, the focus selector is generally a user interface component (or contact on a touch screen display) that is controlled by the user to convey what the user desires. User interface interaction (eg, by indicating to the device the components of the user interface that the user is intended to interact with). For example In other words, when a press input is detected on a touch-sensitive surface (eg, a touchpad or a touchscreen), the focus selector (eg, cursor, contact, or selection box) will be indicated above the respective button. The user is intended to activate the individual buttons (as opposed to other user interface components shown on the display of the device).

As used in the specification and claims, the term "characteristic strength" of a contact refers to a feature based on contact of one or more intensities of contact. In some embodiments, the feature strength is based on a plurality of intensity samples. The feature strength is based on a predefined number of intensity samples, as appropriate, or relative to a predefined event (eg, after detecting a contact, before detecting the lift of the contact, before or after the start of the movement detecting the contact) a predetermined period of time (eg, 0.05 seconds, 0.1 seconds, 0.2 before the end of the contact is detected, before or after the intensity of the contact is detected to increase, and/or before or after the intensity of the contact is detected to decrease) (eg, 0.05 seconds, 0.1 seconds, 0.2) A collection of intensity samples collected during seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the strength of the contact, the mean value of the strength of the contact, the average of the strength of the contact, and the first 10th percentile of the strength of the contact. The value at one-half of the maximum value of the strength of the contact, the value at 90% of the maximum value of the strength of the contact, or the like. In some embodiments, the duration of the contact is used to determine the intensity of the feature (eg, when the feature intensity is the average of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more intensity thresholds to determine if the user has performed an operation. For example, the set of one or more intensity thresholds can include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic strength that does not exceed the first threshold results in a first operation, and a contact having a characteristic strength that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, And having a contact that exceeds the characteristic strength of the second threshold results in a third operation. In some embodiments, the comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (eg, whether to perform a separate operation or to abandon the individual operation) instead of using It is determined whether the first operation or the second operation is performed.

In some embodiments, a portion of the gesture is identified for the purpose of determining feature strength. For example, the touch-sensitive surface can receive a continuous slip contact that transitions from the starting position and reaches the end position, at which point the contact strength increases. In this example, the characteristic intensity of the contact at the end location may be based only on one portion of the continuous slip contact rather than the entire slip contact (eg, only the portion of the slip contact at the end location). In some embodiments, a smoothing algorithm can be applied to the intensity of the slip contact prior to determining the feature strength of the contact. For example, the smoothing algorithm may include one or more of the following: an unweighted moving average smoothing algorithm, a triangle smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, such smoothing algorithms eliminate narrow spikes or dips in the intensity of the slip contact for the purpose of determining feature strength.

The intensity of the contact on the touch-sensitive surface can be characterized relative to one or more intensity thresholds such as contact detection intensity threshold, shallow compression intensity threshold, deep compression intensity threshold Value and / or one or more other intensity thresholds. In some embodiments, the shallow press intensity threshold corresponds to the strength of the device that will perform the operations typically associated with clicking a physical mouse or trackpad button. In some embodiments, the deep press strength threshold corresponds to the strength at which the device will perform an operation that is different from the operations typically associated with clicking a button of a physical mouse or track pad. In some embodiments, when the detected contact has a threshold below the shallow press intensity (eg, and above the nominal contact detection intensity threshold, below the nominal contact detection intensity threshold, When the characteristic intensity of the contact is detected again, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an operation associated with the shallow press intensity threshold or the deep press intensity threshold. . In general, unless otherwise stated, the intensity thresholds are consistent between different sets of user interface patterns.

The intensity of the characteristic intensity of the contact from the intensity below the shallow press strength threshold to the intensity between the shallow press intensity threshold and the deep press strength threshold is sometimes referred to as the "light press" input. The characteristic strength of the contact increases from the intensity below the threshold of the deep press strength to a higher than the deep press The strength of the compressive strength threshold is sometimes referred to as the "deep press" input. The intensity of the contact characteristic increases from the intensity below the threshold of the contact detection intensity to the intensity between the threshold of the contact detection intensity and the threshold of the shallow compression intensity, which is sometimes referred to as detecting the touch surface. contact. The decrease in the intensity of the feature from the intensity above the threshold of the detection intensity to the intensity below the threshold of the contact detection intensity is sometimes referred to as the detection of the lift from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more are performed in response to detecting a gesture comprising a respective press input or in response to detecting a respective press input performed with a respective contact (or a plurality of contacts) Operation wherein the respective press inputs are detected based at least in part on the detected intensity of the contact (plurality of contacts) being increased above the press input intensity threshold. In some embodiments, the respective operations are performed in response to detecting that the intensity of the respective contacts increases above the press input intensity threshold (eg, "slide down" for each press input). In some embodiments, the press input includes the intensity of the respective contact being increased above the press input intensity threshold and the intensity of the contact subsequently decreasing below the press input intensity threshold, and in response to detecting the intensity of the respective contact Lower the pressure input below the threshold to perform separate operations (for example, "push up" for each press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," where the device defines or selects a hysteresis strength threshold (eg, hysteresis strength) that has a predefined relationship to the press input intensity threshold. The threshold is lower than the press input threshold by X intensity units, or the hysteresis strength threshold is 75%, 90% of the press input intensity threshold or a reasonable ratio). Thus, in some embodiments, the press input includes the intensity of the respective contact increasing above the press input intensity threshold and the intensity of the contact subsequently decreasing below the hysteresis strength threshold corresponding to the press input intensity threshold, and responding Perform separate operations (eg, "swipe up" for each press input) by detecting the intensity of the individual contacts and then decreasing below the hysteresis strength threshold. Similarly, in some embodiments In the case, only the intensity of the contact detected by the device increases from the intensity at or below the hysteresis strength threshold to the intensity at or above the threshold of the compression input intensity and the intensity of the contact is subsequently lowered to be at or below A press input is detected at the intensity of the hysteresis strength, and a separate operation is performed in response to detecting the press input (eg, an increase in the strength of the contact or a decrease in the strength of the contact, as the case may be).

For ease of explanation, the description in response to a press input associated with pressing an input intensity threshold or an operation performed in response to a gesture including a press input is triggered in response to detecting any of the following: contact The strength is increased above the threshold value of the pressing input intensity; the intensity of the contact increases from the intensity lower than the hysteresis strength threshold to the intensity higher than the pressing input intensity threshold; the contact strength decreases below the pressing input intensity threshold; And/or the strength of the contact is reduced below the hysteresis strength threshold corresponding to the press input intensity threshold. Additionally, in an example where the operation is described as being performed in response to detecting that the intensity of the contact decreases below the threshold of the pressed input intensity, the intensity of the detected contact is reduced to correspond to and below the threshold of the pressed input intensity. The value is below the threshold value and the operation is performed as appropriate.

1. Battery user interface

The battery user interface described below is illustrated by the device 500 in response to an exemplary sequence of screens displayed for determining various battery levels and detecting various user inputs. In these sequences, the arrows indicate the order in which the screens are displayed.

a. Display battery warning

In some embodiments, a personal electronic device such as device 500 can have one or more batteries collectively referred to as a battery. Device 500 can determine if its battery level is at or below a threshold. In some embodiments, device 500 can monitor battery power continuously or intermittently to determine if battery power is at or below a threshold. In some embodiments, device 500 can receive information indicating that the battery level is at or below a threshold.

Figure 6 depicts device 500 in response to determining whether battery power is at or below a threshold An exemplary screen 610 is displayed on touch screen 504. As shown in FIG. 6, initially, touch screen 504 can be inactive. In some embodiments, when the touch screen 504 is inactive, it may not respond to the touch input or may not actively display the content. In some embodiments, when the touch screen 504 is inactive, it is off. Device 500 can determine that battery power is at or below a threshold when touch screen 504 is inactive. Depending on the determination that the battery level is at or below the threshold, device 500 can alert the user that the battery is low by causing a user-perceivable tactile output 606 (such as vibration) on device 500. In some embodiments, instead of causing a tactile output, device 500 can cause an audible or visual output to alert the user that the battery is low.

In some embodiments, the threshold may be a percentage of the total battery power. In some embodiments, the total battery power can be the maximum battery capacity; that is, the battery is fully charged. In this scenario, the battery is fully charged when the battery reaches the threshold of 0% of the total battery power.

In some embodiments, the total battery power may be the maximum battery power of the battery minus the battery capacity reserve, wherein the reserve amount is reserved for performing basic operations such as displaying the current time. In this scenario, when the battery reaches 0% of the total battery power, the battery can still contain the reserve capacity.

The total battery power can be a constant value or can be attributed to temperature or degradation as a function of time. In some embodiments, determining whether the battery power is at or below a threshold includes determining whether the battery has dropped below a threshold or falling below a threshold, and determining whether the battery has risen to a threshold when charging Contrast.

Returning to FIG. 6, after device 500 has determined that the battery level is at or below the threshold and causes tactile output 606, the user can respond to the tactile output by providing an input to device 500. In response to receiving data indicative of input from the user within a predetermined time interval after the tactile output, device 500 can display a screen 610 having a battery alert 612. (The dotted line shown in FIG. 6 is intended to indicate the content of the battery alert, but may not be displayed on the touch screen 504). In some embodiments, displaying battery alert 612 involves displaying an animation that causes battery alert 612 to slide upward from the bottom of touch screen 504.

In some embodiments, the input from the user can be a movement of device 500 that can be detected by an accelerometer and/or a gyroscope on device 500. Such movement may correspond to the user moving the device 500 to a location where the user can view the touch screen 504. This movement may include rotation and/or translation of the device 500. For example, if the device 500 is worn on the wrist of the user, the movement may correspond to the user raising his or her wrist for viewing the touch screen 504. The technique for detecting an elevation gesture is described in U.S. Provisional Patent Application Serial No. 62/026,532, entitled "Raise Gesture Detection in a Device", filed on Jul. 18, 2014. Incorporated by reference.

In other embodiments, the user input can be a touch on the touch screen 504, or one or more input mechanisms can be pressed and/or rotated.

Battery alert 612 includes a visual cue 614 indicating battery power. In this example, the visual cue includes a percentage of the total battery power. Battery alert 612 also includes a low battery message 616.

As previously discussed, device 500 can display battery alert 612 in response to receiving a data indicative of user input within a predetermined time interval after device 500 causes a tactile output. In some embodiments, the predetermined time interval can be in the range of 0 seconds to 3 minutes. In other examples, the predetermined time interval may be in the range of 0 seconds to 1 minute. In other examples, the predetermined time interval may be set by the user or may be determined by device 500 based on previous user behavior, such as the average number of previous elapsed times before the user provided input.

The sequence depicted in FIG. 6 may correspond to a user who perceives the tactile output caused by device 500 wishing to quickly view battery related information and thus move device 500 to be suitable for viewing the touch screen for a predetermined time interval. The situation when in the position of 504.

If device 500 causes a tactile output and then does not detect user input within a predetermined time interval after the tactile output, device 500 may remain in its initial inactive state without The screen 610 is displayed. This context may correspond to situations when the user does not wish to quickly view battery related information and therefore does not move device 500 to a location suitable for viewing the touch screen 504 after sensing the tactile output.

In some embodiments, device 500 can cause a first tactile output in response to detecting that the battery charge is at or below a first predetermined threshold, and then in response to detecting that the battery charge is at or below a second predetermined The threshold value causes a second tactile output, wherein the second predetermined threshold is lower than the first predetermined threshold. Therefore, the device 500 can repeatedly warn the user that the battery is low.

In some embodiments, the first predetermined threshold is 10% of the total battery power and the second predetermined threshold is 5% of the total battery power. In some embodiments, device 500 can cause a tactile output at other predetermined thresholds.

In some embodiments, the battery alert in response to detecting a user input display may depend on a predetermined threshold. For example, the exemplary battery alert depicted in FIG. 6 corresponding to a situation where the threshold is 10% of the total battery power includes an indication of threshold 614 and low battery message 612. In contrast, as shown in FIG. 7A, an exemplary battery alert displayed for a condition where the threshold is 5% of the total battery power may include message 710: if device 500 subsequently determines that the battery charge is at or below a minimum The battery power (such as approximately 0% of the total battery power) will automatically enter the low power mode.

As shown in FIG. 7B, in response to a determination that the battery level is at or below the minimum battery level, device 500 can automatically enter a low power mode and display a screen 704. Screen 704 includes current time 706 and may include an indication 708 that device 500 is in a low power mode. The low power mode is described in more detail with reference to FIGS. 10A through 10B.

In some embodiments, device 500 may display a screen 712 in response to a determination that battery power is at or below a minimum battery level, as depicted in FIG. 7C. Screen 712 includes a confirmation visual cue 716 for confirming that the user wishes to place device 500 in a low power mode. In response to detecting the selection of the confirmation visual cue 716, the device 500 can enter the low power mode and display A screen 704 is shown.

b. Unblock the battery warning

In some embodiments, when screen 610 is displayed (as shown in FIG. 6), device 500 can release battery alert 612 if device 500 receives data indicative of a second user input. Disabling the battery alert 612 can include removing the battery alert from the touchscreen 504. In some embodiments, disarming the battery alert 612 can include displaying an animation that causes the battery alert 612 to slide off the bottom of the touchscreen 504.

In some embodiments, the second user input can correspond to the movement of device 500. Returning to the example in which the device 500 is worn on the wrist, the second user input can correspond to the user moving the device 500 away from the viewing position by, for example, rotating the device 500 away from the position for viewing or lowering its wrist. Such scenarios may correspond to situations in which a user who has viewed a battery alert does not wish to continue viewing or interacting with device 500 and thus mobile device 500 leaves the viewing position. Device 100 can then return to an inactive state to conserve power.

In some embodiments, the user can also release the battery alert by contacting the touch screen 504. As shown in FIG. 8, if the device 500 detects the contact on the touch screen 504 when the screen 610 is displayed, the device 500 can slide the battery alarm 612 down on the touch screen 504 and display the release indicator. 802. The contact may include a touch detected on the touch screen 504 at the first location, and then touch the first position on the touch screen 504 to the touch without interrupting the contact of the detected touch The movement of the second position is followed by the release of the touch (eg, lifting). For example, the movement can be a substantially downward slip or toggle on the touch screen 504. In some embodiments, device 500 may release the battery alert if the user continues to slide down or toggle after the release indicator is displayed.

In some embodiments, device 500 may require the user to slip or toggle most or all of the path down the touchscreen 504 to release battery alert 612. For example, device 500 can determine if the movement of the touch exceeds a threshold distance. If the movement exceeds the threshold distance, the device 500 can release the battery alert in response to detecting the release of the touch. If moving Not exceeding the threshold distance, in response to detecting the release of the touch, the device 500 can slide the battery alert to its original position on the touch screen 504 without disabling the battery alert 612. While the above embodiments are described with respect to sliding down the warning in response to a sloping or swiping, it will be understood by those skilled in the art that any other orientation is contemplated for both the sliding direction and the slidability.

In some embodiments, device 500 can respond to different de-energized inputs in different manners (such as indicating the user's detection of the data on the touchscreen 504 that is sliding the mobile device 500 away from the viewing position). For example, if the device 500 detects that the user is moving the device 500 away from the location for viewing the device 500, the device 500 can assume that the user is no longer viewing the touchscreen 504, and thus can remove the battery alert The touch screen 504 is not activated thereafter. In contrast, if device 500 detects a touch on touch screen 504, followed by a touch movement (such as a downward slip or toggle), device 500 can assume that the user is still actively viewing the touch. Control screen 504, and as shown in FIG. 8, device 500 may instead display home screen 804 or another screen after the battery alert is removed.

c. Display additional battery information

Turning now to FIG. 9, as previously discussed with respect to FIG. 6, device 500 can display battery alert 612 in response to detecting user input within a predetermined time interval following the tactile output caused by device 500. If the device 500 does not detect the second user input during the second predetermined time interval after the battery alert 612 is displayed, the device 500 can display the screen 906 on the touch screen 504. For example, the second user input can be information indicating that the user has moved away from the viewing position by lowering the device 500 or rotating the device. Thus, if the user does not move device 500 after battery alert 612 is displayed, device 500 can display screen 906. This scenario may correspond to a situation where a user who has viewed battery alert 612 wishes to view additional battery related information and therefore does not release battery alert 612. Instead, the user maintains the device 500 in the viewing position and waits for additional battery related information to be displayed on the touch screen 504 after a second predetermined time interval. For example, the second predetermined time interval It can be in the range of 3 seconds to 10 seconds.

Screen 906 includes an indication 902 of threshold values and may include an indication 904 of the estimated amount of remaining time before device 500 enters a low power mode, such as described with respect to Figures 7A-7C. In some embodiments, for example, device 500 can determine an estimated amount of remaining time based on current battery power and average power consumption of device 500, based on battery discharge rate, or based on other factors.

The device 500 can also display a display 906 in response to detecting contact with the touch screen 504 while the battery alert 612 is being displayed. In this scenario, the user may not wish to wait for a second predetermined time interval that elapses before viewing additional battery related information, and instead, touch the touch screen 504 to invoke a direct display of additional battery information. In response to detecting contact with the touch screen 504, the device 500 can display a picture 906.

In some embodiments, the contact used to invoke display of screen 906 is an upward slip on touch screen 504. In other examples, the contact is a touch (eg, a finger tap) on the touch screen 504 at a location corresponding to the battery alert 612. While the above embodiments are described in response to an upward slip or toggle, those of ordinary skill in the art will appreciate that any other orientation is also contemplated for slip direction.

2. Low power mode

As previously discussed with respect to Figures 7A-7B, device 500 can automatically enter a low power mode upon detecting that the battery level is at or below a threshold, or can be responsive to detecting a visual cue selection (eg, for example, Figure 7C) , Figure 11 and Figure 12) enter the low power mode. The low power mode can be a mode in which device 500 operates to reduce power consumption and extend battery life. In some embodiments, when in a low power mode, device 500 may only display a time of day and may include an indication that device 500 is in a low power mode. Thus, in such embodiments, the ability to display the current time is saved, but other functionality of device 500 can be disabled to provide a maximum duration for displaying the time.

In some embodiments, device 500 can be operated when operating in a low power mode The device 500 responds to user input in different ways when operating in the normal power mode. For example, when device 500 is operating in a normal power mode, device 500 can respond to input in a normal manner, such as by displaying an application icon, launching an application, performing various functions, and the like. For example, such inputs may include input from one or more input mechanisms (eg, buttons) 506, 508, contacts on touch screen 504, or information received from an accelerometer or gyroscope. In contrast, when operating in a low power mode, device 500 can wait for (same) input by displaying a single particular output back and forth. In some embodiments, device 500 can power up its display to display only the current time and/or its indication of operation in the low power mode when responding to user input while in low power mode. In some embodiments, device 500 can respond to user input in different ways depending on whether the battery level drops below the first battery threshold or falls below the second battery threshold.

FIG. 10A depicts an example in which device 500 detects a particular input on input mechanism 506 while operating in a normal power mode, such as depression, and responds to this particular input by displaying home screen 1002. 10B depicts the device 500 detecting the same particular input on the input mechanism 506 while operating in the low power mode and indicating that the display device 500 is in a low power mode by displaying the current time and optionally instead of displaying the home screen. 1002 to respond to an instance of this particular input.

In some embodiments, device 500 can display the time in a first color before determining that the battery charge is at or below a threshold, and after determining that the battery charge is at or below a threshold, is different from the first color. The second color shows the time. This technique can provide the user with a visual indication of whether the device 500 is operating in a low power mode, and can reduce the device when the power required to display the time in the second color is lower than the power required to display the time in the first color. 500 power consumption.

In some embodiments, once device 500 enters a low power mode, device 500 can reduce the number of pixels used to display time. This reduction in pixels reduces the power required to display the current time.

In some embodiments, device 500 can combine the above-described techniques for reducing the power required to display time while in a low power mode; that is, device 500 can determine that battery power is at or below a threshold and Different colors are then used to display the time, and once device 500 enters the low power mode, fewer pixels are used to display the time.

In some embodiments, when device 500 is in a low power mode, device 500 can change the position of the time displayed on the display to prevent burn-in of the display while using the position of the displayed time to provide the user with information about the current A quick visual reminder of the date and time. It is worth noting that in these embodiments, the change in position over the display time provides more than a simple screen protection mechanism that, for example, randomly changes the display position to "pop" the displayed text or visual cues around the display. To prevent pre-burning. In such a simple screen protection mechanism, the position of change over the display time is independent of the current date and time, and can be disgusting or upset by the user in displaying time in a relatively unpredictable or unintuitive position on the display. In contrast, in some embodiments, device 500 can convert or animate the displayed time such that a time proportional to the date time is displayed at a location ranging from the "top" of the display to the "bottom" of the display. For example, a time of 00:01 (one minute after midnight on a 24-hour clock) can be displayed near the top of the display, and a time of 23:59 can be displayed near the bottom of the display. In this case, since the display position of time is related to the date and time, the user can quickly estimate or discriminate the approximate date and time by performing a panning at a vertical placement of the displayed time. Similarly, device 500 can display a time proportional to the date and time at a position ranging from "left" of the display to "right" of the display, or can be displayed at a position diagonally across the display. The proportion of time. Those skilled in the art will appreciate that there are a number of ways to determine the display position based on date and time. This display method enhances human-computer interaction because the machine prevents pre-burning of the display without the user being bored with the position of the displayed time.

3. Enter and exit low power mode

In some embodiments, device 500 can respond to detecting that the battery level is at or below The threshold is automatically entered into the low power mode as described with respect to Figures 7A-7B. In some embodiments, device 500 can initiate a tactile output to alert the user that the device is entering a low power mode and then automatically enter a low power mode.

In some embodiments, as described with respect to FIG. 7C, in response to detecting that the battery level is at or below a threshold, device 500 can display a screen 712 with a confirmation visual cue 716 prior to entering the low power mode, thereby requesting use. It is confirmed that it wishes to place the device 500 in a low power mode. In response to detecting the selection of the confirmation visual cue 716, the device 500 enters a low power mode.

If the device 500 enters the low power mode after detecting that the battery level is at or below a threshold level, such as by automatically entering a low power mode or in response to detecting a selection of a confirmation visual cues, as described above, The device 500 can then automatically exit the low power mode when the battery is recharged above the threshold. For example, the threshold can be 10%, 15%, 20%, or 30% of the total battery power.

In some embodiments, device 500 can provide a user interface that allows a user to manually place device 500 in a low power mode. For example, a user may wish to place device 500 in a low power mode in the following situations: the user does not need most of the functionality of device 500, but still desires to utilize the timing function of device 500 and/or desire to extend the battery of device 500. life. For example, a user without a battery charger during travel may wish to reduce power usage on device 500 by placing device 500 in a low power mode to keep device 500 operating for extended periods of time.

FIG. 11A depicts a sequence of devices 500 that may be displayed to allow a user to manually place device 500 in a low power mode, in accordance with some embodiments. In response to detecting user input, device 500 can display screen 1102. For example, the user input can be a slip on the illustrated touch or touch screen 504. Screen 1102 includes a visual cue 1104 indicating the current battery level. In this example, the current battery level is 60% of the total battery power. Visual cue 1104 may include a current battery power indicator and/or current battery level The sensibility meter, in this case, is indicated by the percentage (approximately 60%) of the circle shown as bold.

In response to detecting the second user input, device 500 can display a picture 1106 that includes a visual cue 1108 that will place device 500 in a low power mode. In response to detecting the selection of a visual cue, device 500 can enter a low power mode. In some embodiments, the selection of visual cue 1108 includes a touch or slip on touch screen 504 at a location corresponding to visual cue 1108. In some embodiments, when device 500 enters a low power mode, device 500 displays an indication of time and device 500 in a low power mode.

FIG. 11B depicts a sequence of devices 500 that may be displayed to allow a user to manually place device 500 in a low power mode, in accordance with some embodiments. In response to detecting user input, device 500 can display screen 1202. In some embodiments, the user input can be a touch of the icon on the touch screen 504. For example, the user input is a sliding upward from the bottom edge of the touch screen 504, or a left-to-right or right-to-left slip from the edge of the touch screen 504. Screen 1202 includes a visual cue 1204 indicating the current battery level. In this example, the current battery power is 60% of the total battery power. Screen 1202 also includes a visual cue 1206 for placing device 500 in a low power mode.

In some embodiments, in response to detecting the selection of visual cue 1206, device 500 can display picture 1208. For example, the selection of visual cues 1206 can be a touch or slip on the touch screen 504 at a location corresponding to visual cues 1206. Screen 1208 includes a visual cue 1214 for confirming that device 500 should enter a low power mode, and a visual cue 1216 for entering the aforementioned placement in a low power mode. In response to detecting the selection of visual cues 1214, device 500 can enter a low power mode. For example, the selection of visual cues 1214 can be a touch or slip on the touch screen 504 at a location corresponding to visual cues 1214. In response to detecting the selection of visual cue 1216, device 500 returns to screen 1202 in the display. For example, the selection of visual cues 1216 is a touch or slip on the touch screen 504 at a location corresponding to visual cues 1216.

FIG. 12A depicts another sequence of pictures that device 500 can display to allow a user to manually place device 500 in a low power mode. In response to detecting user input, device 500 can display screen 1202. In some embodiments, the user input can be depressed by the input mechanism 508 or 506. Screen 1202 includes a visual cue 1204 for placing device 500 in a low power mode. In response to detecting the selection of visual cues 1204, device 500 can enter a low power mode. In some embodiments, the selection of visual cues 1204 includes a touch or slip on the touchscreen 504 at a location corresponding to visual cues 1204. In some embodiments, when device 500 enters a low power mode, device 500 displays an indication of time and device 500 in a low power mode.

In some embodiments, visual cues 1204 for placing device 500 in a low power mode are disabled on screen 1202 while device 500 is being charged. For example, when device 500 is connected to a power source, visual cues 1204 are disabled on screen 1202 and cannot be selected. As another example, when device 500 is connected to a power source, visual cue 1204 is replaced with a different visual cue indicating that the battery is being charged. In both instances, the user cannot manually place device 500 from low frequency mode from screen 1202.

In some embodiments, the screen 1202 also includes a shutdown visual cue 1206 for shutting down the device 500, a locked visual cue 1208 for locking and/or unlocking the device 500, and for deselecting and returning to the screen 1004 as appropriate. The visual cue 1210 is cancelled.

In some embodiments, the availability of the locked visual cue 1208 on the screen 1202 is based on one or more settings of the device 500. An exemplary device that affects the display of visual cues 1208 is set as an accessibility feature that improves the functionality of device 500 when worn on a prosthesis (or in other use scenarios where device 500 is in insufficient contact with the skin of the user). If device 500 is configured to automatically detect whether it is worn by a human user, locked visual cue 1208 is not displayed on screen 1202. In contrast, if device 500 is set to bypass detection of whether it is worn by a human user, locked visual cue 1208 is displayed on screen 1202 to permit manual locking of the device.

If the lock visual cue 1208 is displayed on the screen 1202, the device 500 allows the user to manually lock the device by selecting to lock the visual cue 1208. As shown in FIG. 12A, when device 500 is unlocked, picture 1202 includes a locked visual cue 1208 for locking device 500. In response to detecting the selection of the locked visual cues 1208, device 500 becomes locked. In some embodiments, the selection of the locked visual cue 1208 includes a touch or slip on the touch screen 504 at a location corresponding to the locked visual cue 1208. In some embodiments, the locking visual cue 1208 includes a slider switch, and the selection of the locking visual cue 1208 includes a touch or slip of the toggle switch on the touch screen 504. In some embodiments, the locked device 500 displays a picture 1006 to indicate that the device is locked, as shown in Figure 12B.

FIG. 12B depicts a sequence in which device 500 can be displayed to allow a user to manually unlock a picture of device 500. For example, when device 500 is locked, the user can access screen 1202 by launch button 508. Screen 1202 includes a visual cue 1208 for unlocking device 500. Visual cue 1208 optionally indicates the current locked state of device 500. For example, visual cue 1208 can have the associated term "locked." For example, visual cue 1208 can be displayed as a slider switch in its locked position. In response to detecting the selection of visual cue 1208, device 500 initiates an unlock process. In some embodiments, when device 500 initiates an unlock process, device 500 requests a password, as shown in screen 1212.

In some embodiments, device 500 may allow a user to place device 500 in a low power mode without using a user interface or viewing touch screen 504. For example, device 500 can enter a low power mode in response to detecting user input on one or more input mechanisms. As discussed with respect to Figures 5A-5B, in some embodiments, device 500 includes two input mechanisms (such as buttons) 506, 508. In such embodiments, in response to detecting that the user has pressed the two input mechanisms 506, 508 simultaneously or nearly simultaneously, the device 500 can enter a low power mode. In some embodiments, device 500 can respond to detecting only An input mechanism is pressed or rotated or in response to detecting a different sequence or combination of pressure or rotation of the input mechanism into a low power mode.

If device 500 is in a low power mode and the battery level is above the minimum battery level, device 500 can allow the user to cause device 500 to manually exit the low power mode without recharging the battery. In some embodiments, device 500 may exit the low power mode in response to detecting one or more input mechanisms 506, 508 being depressed or rotated. In some embodiments, device 500 can determine whether one or more input mechanisms are under pressure or rotation for a threshold duration. If the duration exceeds the threshold, device 500 can exit the low power mode. Otherwise, device 500 can remain in a low power mode. Thus, in some examples, for example, a user may cause device 500 to manually exit a low power mode by pressing and holding one or more buttons on device 500.

If the battery of device 500 is at or below the minimum battery level - such as approximately 0% of the total battery power, then, for example, device 500 may ignore the user input requesting to exit the low power mode and may remain in the low power mode until The battery is recharged to the minimum battery level. Device 500 may automatically exit the low power mode after the battery has been recharged to be at or above the minimum battery level, or may exit the low power mode in response to detecting a user input as described above.

4. Processing procedures for displaying and managing battery power

FIG. 13 is a flow diagram illustrating a process 1300 for managing battery power levels. The processing program 1300 can be executed at an electronic device (such as devices 100, 300, and/or 500) having a touch-sensitive display screen (eg, Figures 1, 3, and 5). At block 1302, the device determines if the battery level is at or below a threshold level. At block 1304, device 500 causes a tactile output based on a determination that the battery level is at or below a threshold. At block 1306, the device receives information indicative of user input. At block 1308, the device determines if the data was received within a predetermined time interval. At block 1310, the device displays a battery alert based on a determination to receive the data within a predetermined time interval. As the case may be, The battery level of the display when it is not active. Optionally, the device determines if the second material has been received within the second predetermined time interval. Based on the determination that the second data was not received within the second time interval, the device determines an estimated amount of time remaining before the battery power reaches the second threshold. The device displays the amount of time remaining.

It should be noted that the details of the processing procedures described above with respect to processing program 1300 (e.g., Figures 13 and 6) apply in a similar manner to the other processing procedures described herein. For example, the processes 1400 and 1500 can include one or more of the various processes described above with reference to the process 1300. For the sake of brevity, such details are not repeated in the description of other processing procedures. The various methods and techniques described above with respect to method 1300 are visibly implemented as one or more hardware units, such as their hardware units as described with respect to FIG.

FIG. 14 is a flow diagram illustrating a process 1400 for managing battery power levels. The processing program 1400 can be executed at an electronic device (such as devices 100, 300, and/or 500) having a touch-sensitive display (eg, Figures 1, 3, and 5). At block 1402, the device determines if the battery level is at or below a threshold level. At block 1404, the device enters a low power mode based on a determination that the battery level is at or below a threshold. The low power mode is characterized by the device generating the same specific output in response to an input at any of a touch sensitive display, button or rotatable input mechanism, wherein the particular device is in a normal power mode, the particular The output is different from the output produced by the device in response to the same input at any of the touch sensitive display, button or rotatable input mechanism.

Optionally, entering the low power mode includes displaying a confirmation visual cues for confirming that the user wishes to enter the low power mode, and entering the low power mode in response to detecting the selection of the acknowledgment visual cues.

Optionally, the particular output produced in the low power mode includes the current time. Optionally, the particular output produced in the low power mode includes an indication of battery power. Optionally, when in low power mode, the device also responds to self-accelerometers and/or tourbs The snail receives data exceeding a predetermined value to produce a specific output.

It should be noted that the details of the processing procedures described above with respect to processing program 1400 (e.g., FIG. 14 and FIG. 7A through FIG. 7C) are also applied in a similar manner to the other processing procedures described herein. For example, the processes 1300 and 1500 can include one or more of the various processes described above with reference to the process 1400. For the sake of brevity, such details are not repeated in the description of other processing procedures. The various methods and techniques described above with reference to method 1400 can be implemented as one or more units, such as those described with respect to FIG.

15 is a flow chart illustrating a process 1500 for managing battery power levels. The processing program 1500 can be executed at an electronic device (such as devices 100, 300, and/or 500) having a touch-sensitive display (eg, Figures 1, 3, and 5). At block 1502, the device receives a first data indicative of activation of the first input mechanism. At block 1504, the device receives second data indicative of activation of the second input mechanism, wherein the second data is received for a predetermined period of time after receiving the first data. At block 1506, in response to receiving the first data and the second data, the device determines the amount of time remaining before the battery level reaches the threshold and displays the remaining amount of time and a visual cue. At block 1508, the device detects the selection of a visual cue. At block 1510, in response to detecting the selection, the device enters a low power mode. Optionally, when in the low power mode, the device receives data indicative of the depression of the rotatable input mechanism. The device determines the duration of the depression. If the duration exceeds the threshold, the device exits the low power mode.

It should be noted that the details of the processing procedures described above with respect to processing program 1500 (e.g., FIG. 15) are also applied in a similar manner to the other processing procedures described herein. For example, the processes 1300 and 1400 can include one or more of the various processes described above with reference to the process 1500. For the sake of brevity, such details are not repeated in the description of other processing procedures. The various methods and techniques described above with reference to method 1500 are exemplarily implemented as one or more units, such as those described with respect to FIG.

16 shows an illustrative functional block diagram of an electronic device 1600 configured in accordance with the principles of various described embodiments, in accordance with some embodiments. According to some embodiments, the functional blocks of electronic device 1600 are configured to perform the techniques described above. Functional blocks of device 1600 are optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. Those skilled in the art will appreciate that the functional blocks described in Figure 16 may be combined as appropriate or separated into sub-blocks to implement the principles of the various described examples. Accordingly, the description herein supports any possible combinations or separations, or other definitions, of the functional blocks described herein as appropriate.

As shown in FIG. 16 , the electronic device 1600 includes a touch-sensitive display unit 1602 , a battery unit 1606 , a haptic mechanism unit 1608 , and a processing unit 1610 . The processing unit is coupled to the touch-sensitive display unit 1602 and the battery unit 1606 . And a touch mechanism unit 1608. The processing unit 1610 includes a battery power determining unit 1612, a haptic mechanism control unit 1614, a data receiving unit 1616, a time determining unit 1618, and a display enabling unit 1620. Optionally, the electronic device 1600 includes a hardware button unit 1650, a rotatable input mechanism unit 1652, an accelerometer unit 1654, and a gyroscope unit 1656, all of which are coupled to the processing unit 1610. Optionally, the processing unit 1610 includes an input detection unit 1622, an output generation unit 1624, and a power mode unit 1626.

The processing unit 1610 is configured to: (eg, utilize battery power determination unit 1612) determine battery power of battery unit 1606; based on a determination that battery power is at or below a first threshold, (eg, using a haptic mechanism control) Unit 1614) causes tactile mechanism unit 1608 to emit a tactile output; (eg, with data receiving unit 1616) receiving information indicative of user input; (eg, using time determination unit 1618) to determine if a tactile output has been scheduled The data is received during the time interval; and the display of the battery alert on the touch-sensitive display unit 1602 is enabled (eg, with the display enable unit 1620) based on a determination that the data has been received within the predetermined time interval.

In some embodiments, processing unit 1610 is further configured to be in a touch sensitive display The unit 1602 determines the battery level when it is inactive (for example, using the battery power determining unit 1612).

In some embodiments, the data entered by the user is indicated as the first data and the user input is the first user input, and the processing unit 1610 is further configured to: after enabling the display of the battery alert (eg, utilizing The data receiving unit 1616) receives the second data indicating the second user input; (eg, using the time determining unit 1618) to determine whether the second user input is received within the second time interval after the display of the battery alert is enabled. Second data; removing the display of the battery alert from the touch sensitive display unit 1602 (eg, using the display enable unit 1620) based on the determination that the second data has been received during the second time interval; The determination that the second material is not received within the second time interval: (eg, using time determination unit 1618) determines a remaining amount of time before the battery level reaches the second threshold level, and (eg, utilizing Display enable unit 1620) enables display of the remaining amount of time on touch-sensitive display unit 1602.

In some embodiments, the second user input corresponds to movement of the electronic device 1600.

In some embodiments, the processing unit 1610 is further configured to: when the touch sensitive display unit 1602 is displaying a battery alert, (eg, using the input detection unit 1622) to detect a third user input; Detecting the third user input: (eg, using time determination unit 1618) determining a remaining amount of time before the battery level reaches the second threshold level; and (eg, using display enable unit 1620) enabling the The amount of remaining time is displayed on the touch sensitive display unit 1602.

In some embodiments, the third user input is a contact on the touch-sensitive display unit 1602.

In some embodiments, the processing unit 1610 is further configured to detect (eg, the input detection unit 1622) on the touch-sensitive display unit 1602 when the touch-sensitive display unit 1602 is displaying a battery alert. Slip; and in response to detecting the slip, (for example, The display 1620 is enabled to remove the display of the battery alert from the touch sensitive display unit 1602.

In some embodiments, the slip is a substantially downward slip.

In some embodiments, the processing unit 1610 is further configured to: remove the battery alert by enabling (eg, with the display enable unit 1620) enabling display of an animation that causes the battery alert to slide off the screen in the direction of the slip. display.

In some embodiments, processing unit 1610 is further configured to cause display of touch-sensitive display unit 1602 to become inactive by, for example, utilizing display enable unit 1620, being removed from touch-sensitive display unit 1602 Battery warning display.

In some embodiments, processing unit 1610 is further configured to enable battery alerting by enabling display of an animation that causes battery warning to slide up from the bottom of touch-sensitive display unit 1602 (eg, with display enable unit 1620) display.

In some embodiments, processing unit 1610 is further configured to generate a first output in response to an input at touch-sensitive display unit 1602 (eg, with output generation unit 1624) while in a normal power mode (eg, with output generation unit 1624) Generating a second output in response to input at the at least one hardware button unit 1650, and generating a third output in response to input at the rotatable input mechanism unit 1652; and depending on whether the battery level is at or below A determination of the first threshold, (eg, using power mode unit 1626) to enter a low power mode characterized by responding to the touch sensitive display unit 1602, at least one hardware button unit 1650, or a rotatable input A fourth output is generated by an input at any of the mechanism units 1652.

In some embodiments, the fourth output is different from the first output, the second output, and the third output.

In some embodiments, the fourth output includes a display of the current time on the touch-sensitive display unit 1602.

In some embodiments, the fourth output includes a display of the battery level of the battery unit 1606 on the touch-sensitive display unit 1602.

In some embodiments, processing unit 1610 is further configured to: when in a normal power mode: (eg, with data receiving unit 1616) receive at least one of accelerometer unit 1654 and gyroscope unit 1656 The third data, and based on the determination that the third data of at least one of the accelerometer unit 1654 and the gyro unit 1656 exceeds a predetermined value, (eg, using the output generation unit 1624) produces a fifth output.

In some embodiments, processing unit 1610 is further configured to: when in a low power mode: receive (eg, with data receiving unit 1616) from at least one of accelerometer unit 1654 and gyroscope unit 1656 The third data, and based on the determination that the third data of at least one of the accelerometer unit 1654 and the gyro unit 1656 exceeds a predetermined value, (eg, using the output generation unit 1624) produces a fourth output.

The operations described above with reference to FIG. 13 are optionally implemented by the components depicted in FIGS. 1A-1B or 16. For example, the battery power determination operation 1302, the tactile output output operation 1304, and the data reception operation 1306 can be 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 the contact on the touch-sensitive display 112, and the event dispatcher module 174 delivers the event information to the application 136-1. The respective event recognizer 180 of the application 136-1 compares the event information with the respective event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event. , such as the initiation of visual cues on the user interface. Event detector 180 initiates event handler 190 associated with the detection of an event or sub-event when a respective predefined event or sub-event is detected. The event handler 190 can utilize or invoke the data update program 176 or the object update program 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the respective GUI update program 178 to update the content displayed by the application. Similarly, those skilled in the art will be aware of how other processing procedures can be implemented based on the components depicted in Figures 1A-1B.

Figure 17 shows a configuration in accordance with the principles of various described embodiments, in accordance with some embodiments. An exemplary functional block diagram of electronic device 1700. According to some embodiments, the functional blocks of electronic device 1700 are configured to perform the techniques described above. Functional blocks of device 1700 are optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. Those skilled in the art will appreciate that the functional blocks described in Figure 17 may be combined as appropriate or separated into sub-blocks to implement the principles of the various described examples. Accordingly, the description herein supports any possible combinations or separations, or other definitions, of the functional blocks described herein as appropriate.

As shown in FIG. 17, the electronic device 1700 includes a touch-sensitive display unit 1702, a battery unit 1706, a hardware button unit 1708, a rotatable input mechanism unit 1710, and a processing unit 1712 coupled to the touch-sensitive display unit 1702. Battery unit 1706, hardware button unit 1708, and rotatable input mechanism unit 1710. The processing unit 1712 includes a battery power determining unit 1714, a power mode unit 1716, and an output generating unit 1718. Optionally, the electronic device 1700 includes a haptic mechanism unit 1752, an accelerometer unit 1754, and a gyro unit 1756, all of which are coupled to the processing unit 1712. Optionally, the processing unit 1712 includes a display enabling unit 1720, an input detecting unit 1722, a data receiving unit 1724, and a tactile mechanism control unit 1726.

The processing unit 1712 is configured to, when in the normal power mode (eg, with the output generation unit 1718), generate a first output in response to the input at the touch-sensitive display unit 1702, in response to being at least one hard The input at the body button unit 1708 generates a second output, and generates a third output in response to the input at the rotatable input mechanism unit 1710; (eg, using the battery power determining unit 1714) determines the battery level of the battery unit 1706; And determining, based on whether the battery level is at or below a first threshold: (eg, utilizing power mode unit 1716) to enter a low power mode, the low power mode being characterized by responding to at least one of the touch sensitive display unit 1702 A fourth output is produced by input at either the hardware button unit 1708 or the rotatable input mechanism unit 1710.

In some embodiments, entering a low power mode includes: (eg, using display enablement Unit 1720) enable display of an acknowledgment visual cues for entering a low power mode; (eg, using input detection unit 1722) to detect a selection of a visual cues; and in response to detecting the selection, (eg, utilizing a power mode) Unit 1716) enters a low power mode.

In some embodiments, the fourth output is different from the first output, the second output, and the third output.

In some embodiments, the fourth output includes a display of the current time on the touch-sensitive display unit 1702.

In some embodiments, the fourth output includes a display of the battery level of the battery unit 1706 on the touch-sensitive display unit 1702.

In some embodiments, electronic device 1700 further includes at least one of accelerometer unit 1754 and gyroscope unit 1756. Processing unit 1712 is further coupled to at least one of accelerometer unit 1754 and gyroscope unit 1756.

In some embodiments, processing unit 1712 is further configured to: when in a normal power mode: receive (eg, using data receiving unit 1724) from at least one of accelerometer unit 1754 and gyroscope unit 1756 A data, and based on a determination that the first data from at least one of the accelerometer unit 1754 and the gyro unit 1756 exceeds a predetermined value, (eg, using the output generation unit 1718) produces a fifth output.

In some embodiments, processing unit 1712 is further configured to: when in a low power mode: receive second data from at least one of accelerometer unit 1754 and gyroscope unit 1756; from the accelerometer A determination that the second data of at least one of the unit and the gyro unit exceeds a predetermined value (eg, using output generation unit 1718) produces a fourth output.

In some embodiments, the electronic device 1700 further includes a haptic mechanism unit 1752. The processing unit 1712 is coupled to the haptic mechanism unit 1752 and is further configured to cause a tactile sensation (eg, using the haptic mechanism control unit 1726) based on a determination that the battery charge is at or below a first threshold value The mechanism unit 1752 emits a touch on the electronic device 1700 Sense output.

In some embodiments, processing unit 1712 is further configured to enable electronic device 1700 to be in a low power mode (eg, with display enable unit 1720) based on a determination that battery power is at or below a first threshold. The display of the indication.

In some embodiments, processing unit 1712 is further configured to: enable display of the first color in time (eg, with display enable unit 1720) based on a determination that battery power is above a first threshold; and A determination that the battery level is at or below the first threshold (eg, with display enable unit 1720) enables display of a second color that is different from the first color.

In some embodiments, the power required to enable display of the second color for the time is less than the power required to enable display of the first color for the time.

In some embodiments, the display of the enable time with the second color instead of the first color includes (eg, with display enable unit 1720) reducing the number of pixels of touch-sensitive display unit 1702 for displaying the time.

The operations described above with reference to FIG. 14 are optionally implemented by the components depicted in FIGS. 1A-1B or 17. For example, battery power determination operation 1402 and low power mode entry operation 1404 can be implemented by event classifier 170, event recognizer 180, and event handler 190. The event monitor 171 in the event classifier 170 detects the contact on the touch-sensitive display 112, and the event dispatcher module 174 delivers the event information to the application 136-1. The respective event recognizer 180 of the application 136-1 compares the event information with the respective event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event. , such as the initiation of visual cues on the user interface. Event detector 180 initiates event handler 190 associated with the detection of an event or sub-event when a respective predefined event or sub-event is detected. The event handler 190 can utilize or invoke the data update program 176 or the object update program 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the respective GUI update program. 178, to update the content displayed by the application. Similarly, those skilled in the art will be aware of how other processing procedures can be implemented based on the components depicted in Figures 1A-1B.

18 shows an illustrative functional block diagram of an electronic device 1800 configured in accordance with the principles of various described embodiments, in accordance with some embodiments. According to some embodiments, the functional blocks of electronic device 1800 are configured to perform the techniques described above. Functional blocks of device 1800 are optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. Those skilled in the art will appreciate that the functional blocks described in FIG. 18 may be combined as appropriate or separated into sub-blocks to implement the principles of the various described examples. Accordingly, the description herein supports any possible combinations or separations, or other definitions, of the functional blocks described herein as appropriate.

As shown in FIG. 18, the electronic device 1800 includes a touch sensitive display unit 1802, a battery unit 1806, at least two input mechanisms (eg, a first mechanism unit 1808 and a second mechanism unit 1810), and a processing unit 1812. The unit is coupled to the touch sensitive display unit 1802, the battery unit 1806, and at least two input mechanisms (eg, the first mechanism unit 1808 and the second mechanism unit 1810). The processing unit 1812 includes a data receiving unit 1814, a time determining unit 1816, a display enabling unit 1818, an input detecting unit 1820, and a power mode unit 1822. Optionally, the electronic device 1800 includes at least one hardware button unit 1850, a rotatable input mechanism unit 1852, an accelerometer unit 1854, and a gyroscope unit 1856, all of which are coupled to the processing unit 1812. Optionally, the rotatable input mechanism unit 1852 includes a mechanical button unit 1858. Optionally, the rotatable input mechanism 1852 includes a capacitive button unit 1860. Optionally, processing unit 1812 includes an input detection unit 1824, an output generation unit 1826, a power mode unit 1828, and a data reception unit 1830.

Processing unit 1812 is configured to: (eg, with data receiving unit 1814) receive first data indicative of activation of first input mechanism unit 1808; (eg, with data receiving unit 1814) receive indication of second input mechanism unit 1810 The second data that is activated, of which Receiving the second data within a predetermined duration of time from receiving the first data; and in response to receiving the first data and the second data: (eg, using time determination unit 1816) determining that the amount of power at battery unit 1806 is reached A remaining amount of time prior to the first threshold, (eg, with display enable unit 1818) enables display of the remaining amount of time, (eg, with display enable unit 1818) enabling display of visual cues for invoking low power mode The selection of the visual cue is detected (eg, by the input detection unit 1820), and in response to detecting the selection, (eg, using the power mode unit 1822) to enter the low power mode.

In some embodiments, processing unit 1812 is further configured to: in response to detecting a selection, (eg, with display enable unit 1818) enabling display of an indication that electronic device 1800 is in a low power mode, and (eg, utilizing The display enable unit 1818) enables the display of the time.

In some embodiments, the electronic device 1800 further includes at least one hardware button unit 1850 and a rotatable input mechanism unit 1852. The electronic device 1800 is configured to generate a first output in response to an input at the touch sensitive display unit 1802 while in a normal power mode, and to generate a second output in response to an input at the at least one hardware button unit 1850 And generating a third output in response to input at the rotatable input mechanism unit 1852. Processing unit 1812 is further configured to: enter a low power mode based on a determination that battery power is at or below a first threshold: (eg, utilizing power mode 1828), the low power mode being characterized by being responsive to touch sensitivity The input at any of the display unit 1802, the at least one hardware button unit 1850, or the rotatable input mechanism unit 1852 produces a fourth output.

In some embodiments, the fourth output is different from the first output, the second output, and the third output.

In some embodiments, the fourth output includes a display of the current time on the touch-sensitive display unit 1802.

In some embodiments, the fourth output includes the battery level of the battery unit 1806. The display shown on the touch sensitive display unit 1802.

In some embodiments, electronic device 1800 further includes at least one of accelerometer unit 1854 and gyroscope unit 1856.

In some embodiments, processing unit 1812 is further configured to: when in a normal power mode: receive (eg, using data receiving unit 1830) from at least one of accelerometer unit 1854 and gyroscope unit 1856 A data, and based on a determination that the first data of at least one of accelerometer unit 1854 and gyro unit 1856 exceeds a predetermined value, (eg, with output generation unit 1826) produces a fifth output.

In some embodiments, processing unit 1812 is further configured to: when in a low power mode: (eg, with data receiving unit 1830) receive at least one of accelerometer unit 1854 and gyroscope unit 1856 And wherein the fourth output is generated (eg, by the output generation unit 1826) based on a determination that the second data from at least one of the accelerometer unit 1854 and the gyro unit 1856 exceeds a predetermined value.

In some embodiments, the rotatable input mechanism unit 1852 is also depressible. Processing unit 1812 is further configured to detect (eg, with input detection unit 1820) a lower pressure of rotatable input mechanism unit 1852 when in a low power mode; (eg, with time determination unit 1816) The duration of the depression of the rotary input mechanism unit 1852; and exiting the low power mode (eg, using the power mode 1828) based on a determination that the duration of the depression exceeds a predetermined threshold.

In some embodiments, the rotatable input mechanism unit 1852 includes a mechanical button unit 1858 and the depression represents a press on the mechanical button unit 1858.

In some embodiments, the rotatable input mechanism unit 1852 includes a capacitive button unit 1860 and the depression represents a touch on the capacitive button 1860.

The operations described above with reference to Figure 15 are performed as appropriate by the components depicted in Figures 1A-1B or 18. For example, the signal receiving operation 1502, the time determining operation 1506, and the detecting operation 1508 can be performed by the event classifier 170, the event recognizer 180, and the event location. The program 190 is implemented. The event monitor 171 in the event classifier 170 detects the contact on the touch-sensitive display 112, and the event dispatcher module 174 delivers the event information to the application 136-1. The respective event recognizer 180 of the application 136-1 compares the event information with the respective event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event. , such as the initiation of visual cues on the user interface. Event detector 180 initiates event handler 190 associated with the detection of an event or sub-event when a respective predefined event or sub-event is detected. The event handler 190 can utilize or invoke the data update program 176 or the object update program 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the respective GUI update program 178 to update the content displayed by the application. Similarly, those skilled in the art will be aware of how other processing procedures can be implemented based on the components depicted in Figures 1A-1B.

For the purposes of explanation, the foregoing description has been described with reference to the specific embodiments. However, the above illustrative statements are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its application. This will enable those skilled in the art to make the best use of the various embodiments and various embodiments of the various modifications.

Although the present invention and its embodiments are described with reference to the accompanying drawings, it will be understood that Such changes and modifications are to be understood as included within the scope of the invention, and the examples are understood to be defined by the scope of the claims.

Claims (90)

A method comprising: receiving a user input; and responding to receiving the user input associated with displaying a different user interface when an electronic device is operating in a normal power mode of operation: according to the electronic device Operating in one of the low power modes different from the normal power mode of operation, displaying the current time and the electronic device on the display simultaneously without displaying the individual user interface on the display One of the low power modes indicates; and the individual user interface is displayed on the display in accordance with the electronic device operating in the normal power mode of operation. The method of claim 1, wherein the user input is a button press input. The method of claim 1 or 2, wherein the individual user interface is a home screen user interface. The method of claim 1 or 2, wherein the individual user interface comprises one or more application icons. The method of claim 1 or 2, wherein the individual user interface comprises an application user interface. The method of claim 1 or 2, further comprising: determining to perform a first function according to an operation mode of the electronic device operating in one of the normal power operation modes; and operating the operation mode according to an operation mode of the electronic device One of the low power modes decides to abandon the execution of the first function. The method of claim 1 or 2, further comprising: before receiving the user input and when the electronic device is not operating at the low battery In the power mode, determining a battery power of one of the batteries of the electronic device; entering the low power mode according to the battery power being lower than a threshold; and discarding the low according to the battery power not lower than the threshold Power mode. An electronic device comprising: a display; one or more processors; and a memory for storing the one or more programs configured to execute the one or more programs by one or more processors The instructions include: receiving a user input; and receiving, in response to receiving, the user input associated with displaying a different user interface when the electronic device is operating in a normal power mode of operation: operating according to the electronic device Determining, in one of the low power modes different from the normal power operation mode, displaying the current time and the electronic device at the low level on the display without displaying the individual user interface on the display One of the power modes indicates; and the individual user interface is displayed on the display in accordance with the electronic device operating in the normal power mode of operation. The electronic device of claim 8, wherein the user input is a button press input. The electronic device of claim 8 or 9, wherein the individual user interface is a home screen user interface. The electronic device of claim 8 or 9, wherein the individual user interface comprises one or more application icons. The electronic device of claim 8 or 9, wherein the individual user interface comprises an application user interface. The electronic device of claim 8 or 9, wherein the processing unit is further configured: Performing a first function according to one of the operation modes of the electronic device operating in the normal power operation mode; and determining to perform the first operation according to one of the operation modes of the electronic device operating in the low power mode A feature. The electronic device of claim 8 or 9, wherein the processing unit is further configured to: determine a battery of the electronic device before receiving the user input and when the electronic device is not operating in the low power mode One of the battery powers; entering the low power mode according to the battery power being below a threshold; and abandoning the low power mode according to the battery power not lower than the threshold. A non-transitory computer readable storage medium, comprising: one or more programs for executing by one or more processors having one of a display, the one or more programs comprising the following instructions: receiving a User input; and when the electronic device is operating in a normal power mode of operation, in response to receiving the user input associated with displaying a different user interface: operating according to the electronic device being different from the normal power One of the low power modes of the operating mode determines that a current time and one of the indications of the electronic device in the low power mode are simultaneously displayed on the display without displaying the individual user interface on the display. And displaying the individual user interface on the display in accordance with the operation of the electronic device in the normal power mode of operation. A non-transitory computer readable storage medium as claimed in claim 15, wherein the user input is a button press input. A non-transitory computer readable storage medium as claimed in claim 15 or 16, wherein the individual The user interface is a home screen user interface. The non-transitory computer readable storage medium of claim 15 or 16, wherein the individual user interface comprises one or more application icons. The non-transitory computer readable storage medium of claim 15 or 16, wherein the individual user interface comprises an application user interface. The non-transitory computer readable storage medium of claim 15 or 16, wherein the one or more programs include instructions for: executing one of the normal power operation modes according to an operation mode of the electronic device, executing one a first function; and determining to operate the one of the low power modes according to an operation mode of the electronic device, discarding execution of the first function. The non-transitory computer readable storage medium of claim 15 or 16, wherein the one or more programs include instructions to: before receiving the user input and when the electronic device is not operating in the low power mode, Determining a battery power of one of the batteries of the electronic device; entering the low power mode according to the battery power being lower than a threshold; and discarding entering the low power mode according to the battery power not lower than the threshold. An electronic device comprising: a display; means for receiving a user input; and for correlating receipt and display of a different user interface when the electronic device is operating in a normal power mode of operation The user input to perform the component of: determining that the individual user interface is not displayed on the display according to the electronic device operating in one of the low power modes different from the normal power operation mode In the case of the display, a current time and an indication of the electronic device in the low power mode are simultaneously displayed on the display; and the individual is displayed on the display according to the electronic device operating in the normal power operation mode user interface. The electronic device of claim 22, wherein the user input is a button press input. The electronic device of claim 22 or 23, wherein the individual user interface is a home screen user interface. The electronic device of claim 22 or 23, wherein the individual user interface comprises one or more application icons. The electronic device of claim 22 or 23, wherein the individual user interface comprises an application user interface. The electronic device of claim 22 or 23, further comprising: means for performing a first function according to one of operating in the normal power operation mode of the operating mode of the electronic device; and operating mode according to the electronic device The system operates in one of the low power modes to determine to abandon the device performing the first function. The electronic device of claim 22 or 23, further comprising: means for determining a battery level of one of the batteries of the electronic device prior to receiving the user input and when the electronic device is not operating in the low power mode; And entering the low power mode device according to the battery power being lower than a threshold; and discarding the device entering the low power mode according to the battery power not lower than the threshold. A method comprising: at an electronic device having a touch sensitive display, a battery, at least one hardware button, and a rotatable input mechanism, the electronic device configured to be in a positive In the normal power mode, generating a first output in response to the input at the touch sensitive display, generating a second output in response to the input at the at least one hardware button, and responding to the rotatable Inputting at the input of the mechanism to generate a third output: determining a battery level of the battery; and determining, according to one of the battery levels being at or below a first threshold: entering a low power mode, the low power mode Characterized by generating a fourth output in response to an input at the touch sensitive display, the at least one hardware button, or the rotatable input mechanism. The method of claim 29, wherein entering the low power mode comprises: displaying a visual cues for entering one of the low power modes; detecting one of the acknowledgment visual cues; and responsive to detecting the selection, entering the Low power mode. The method of claim 29 or 30, wherein the fourth output is different from the first output, the second output, and the third output. The method of claim 29 or 30, wherein the fourth output comprises a display of the current time on the touch-sensitive display. The method of claim 29 or 30, wherein the fourth output comprises one of the battery levels of the battery indicating a display on the touch sensitive display. The method of claim 29 or 30, wherein the electronic device further comprises at least one of an accelerometer and a gyroscope. The method of claim 34, further comprising: receiving the first data from the accelerometer and the at least one of the gyroscopes when in the normal power mode; and according to the accelerometer and the gyroscope The first data of at least one of the A determination that exceeds a predetermined value produces a fifth output. The method of claim 35, further comprising: receiving the second data of the accelerometer and the at least one of the gyroscopes when in the low power mode; according to the accelerometer and the gyroscope The determining that the second data of the at least one of the second data exceeds the predetermined value produces the fourth output. The method of claim 29 or 30, wherein the device comprises a tactile mechanism, the method further comprising: causing the tactile mechanism to be in the electronic according to the determination that the battery charge is at or below the first threshold A tactile output is emitted from the device. The method of claim 29 or 30, further comprising: indicating the indication that the electronic device is in a low power mode based on the determination that the battery level is at or below the first threshold. The method of claim 29 or 30, further comprising: displaying the time in a first color according to a determination that the battery power is higher than the first threshold; and according to the battery being at or below the battery One of the thresholds determines that the time is displayed in a second color different from the first color. The method of claim 39, wherein the power required to display the time in the second color is lower than the power required to display the time in the first color. The method of claim 39, wherein displaying the time in the second color instead of the first color comprises reducing a number of pixels of the touch-sensitive display for displaying the time. An electronic device comprising: one or more processors; a memory; a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; and one or more programs, wherein the one or more programs are stored in the memory and configured to use the one Executing by the plurality of processors, the one or more programs including instructions for: generating a first output in response to the input at the touch-sensitive display when in a normal power mode, responding Generating a second output at the input of the at least one hardware button, and generating a third output in response to the input at the rotatable input mechanism; determining a battery level of the battery; and determining the battery according to the battery Determining that the amount of power is at or below a first threshold: entering a low power mode characterized by responding to the touch sensitive display, the at least one hardware button, or the rotatable input mechanism A fourth output is produced by input at either of them. A non-transitory computer readable storage medium storing one or more programs including by having a touch sensitive display, a battery, at least one hardware button, and a rotatable input mechanism When executed by one or more processors of an electronic device, the electronic device is caused to execute an instruction to generate a first output in response to an input at the touch sensitive display when in a normal power mode, Generating a second output in response to the input at the at least one hardware button, and generating a third output in response to the input at the rotatable input mechanism; determining a battery level of the battery; The battery is at or below one of the first thresholds: Enter A low power mode characterized by generating a fourth output in response to an input at the touch sensitive display, the at least one hardware button, or the rotatable input mechanism. An electronic device comprising: a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; responsive to being at the touch sensitive display when the electronic device is in a normal power mode Inputting a first output, generating a second output in response to input at the at least one hardware button, and generating a third output in response to input at the rotatable input mechanism; Determining a component of the battery power of the battery; and determining, based on the battery being at or below a first threshold: a component for entering a low power mode, the low power mode being characterized by A fourth output is generated at an input at the touch sensitive display, the at least one hardware button, or the rotatable input mechanism. An electronic device comprising: one or more processors; a memory; a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; one or more programs, wherein the one or more Programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including The instructions of any of the methods of claims 29 through 41 are as follows. A non-transitory computer readable storage medium storing one or more programs including by having a touch sensitive display, a battery, at least one hardware button, and a rotatable input mechanism When executed by one or more processors of an electronic device, the electronic device is caused to execute an instruction as in any of the methods of claims 29 through 41. An electronic device comprising: a touch sensitive display; a battery; at least one hardware button; a rotatable input mechanism; and means for performing any of the methods of claims 29 to 41. An electronic device comprising: a touch sensitive display unit; a battery unit; at least one hardware button unit; a rotatable input mechanism unit; and a processing unit coupled to the touch sensitive display unit, the battery a unit, the at least one hardware button unit, and the rotatable input mechanism unit configured to: generate a An output, responsive to input at the at least one hardware button unit to generate a second output, and responsive to input at the rotatable input mechanism unit to generate a third output; determining a battery of the battery unit The amount of electricity; and based on whether the battery is at or below one of the first thresholds: Entering a low power mode characterized by generating a fourth in response to an input at any of the touch sensitive display unit, the at least one hardware button unit, or the rotatable input mechanism unit Output. The electronic device of claim 48, wherein entering the low power mode comprises: enabling display of a visual cues for entering one of the low power modes; detecting one of the acknowledgment visual cues; and responding to detecting the selection , enter the low power mode. The electronic device of claim 48 or 49, wherein the fourth output is different from the first output, the second output, and the third output. The electronic device of claim 48 or 49, wherein the fourth output comprises a display of the current time on the touch-sensitive display unit. The electronic device of claim 48 or 49, wherein the fourth output comprises one of the battery levels of the battery unit indicating a display on the touch-sensitive display unit. The electronic device of claim 48 or 49, wherein the electronic device further comprises at least one of an accelerometer unit and a gyroscope unit, and wherein the processing unit is further coupled to the accelerometer unit and the gyroscope unit At least one of them. The electronic device of claim 53, wherein the processing unit is further configured to: receive the first data from the accelerometer unit and the at least one of the gyroscope units when in the normal power mode; and A fifth output is generated based on a determination that the first data from the at least one of the accelerometer unit and the gyro unit exceeds a predetermined value. The electronic device of claim 54, wherein the processing unit is further configured to: receive the second of the accelerometer unit and the at least one of the gyroscope units when in the low power mode Data; generating the fourth output based on a determination that the second data from the at least one of the accelerometer unit and the gyro unit exceeds the predetermined value. The electronic device of claim 48 or 49, wherein the device comprises a tactile mechanism unit, wherein the processing unit is coupled to the tactile mechanism unit, and wherein the processing unit is further configured to: The determination of being at or below the first threshold causes the haptic mechanism unit to emit a tactile output on the electronic device. The electronic device of claim 48 or 49, wherein the processing unit is further configured to: enable the electronic device to be in a low power mode based on the determination that the battery charge is at or below the first threshold value An indication of the indication. The electronic device of claim 48 or 49, wherein the processing unit is further configured to: enable a display of a first color based on a determination that the battery level is greater than the first threshold; and A determination is made that the battery level is at or below one of the first threshold values, and the display of the time is different from the second color of the first color. The electronic device of claim 58, wherein the time required to enable the display of the second color is less than the power required to enable the display of the first color. The electronic device of claim 58, wherein the enabling of the second color instead of the display of the first color comprises: reducing a number of pixels of the touch-sensitive display unit for displaying the time. A method comprising: having a touch sensitive display, a battery, and one of the at least two input mechanisms: Receiving a first data indicating activation of one of the first input mechanisms; receiving second data indicating activation of one of the second input mechanisms, wherein the second data is received during a predetermined time period from receiving the first data And in response to receiving the first data and the second data: determining a remaining amount of time before one of the batteries reaches a first threshold, displaying the remaining amount of time, the display is used to invoke a low power mode One of the visual cues detects a selection of the visual cues and enters the low power mode in response to detecting the selection. The method of claim 61, further comprising: responsive to detecting the selection: displaying the device in an indication of the low power mode, and displaying for a time. The method of claim 61 or 62, wherein the electronic device further comprises at least one hardware button and a rotatable input mechanism configured to respond to the touch sensitive display when in a normal power mode Inputting a first output, generating a second output in response to input at the at least one hardware button, and generating a third output in response to input at the rotatable input mechanism, the method further Including: determining, based on the battery power being at or below the first threshold: entering a low power mode, the low power mode being characterized by responding to the touch sensitive display, the at least one hardware button, or A fourth output is generated by the input at any of the rotatable input mechanisms. The method of claim 63, wherein the fourth output is different from the first output, the second output, and the third output. The method of claim 63, wherein the fourth output comprises a display of the current time on the touch sensitive display. The method of claim 63, wherein the fourth output comprises one of the battery levels of the battery indicating a display on the touch-sensitive display. The method of claim 63, wherein the electronic device further comprises at least one of an accelerometer and a gyroscope. The method of claim 67, further comprising: when in the normal power mode: receiving first data from at least one of the accelerometer and the gyroscope; and according to the accelerometer and the gyroscope A determination that the at least one of the first data exceeds a predetermined value produces a fifth output. The method of claim 68, further comprising: receiving the second data from the accelerometer and the gyroscope when in the low power mode; and from the accelerometer and the gyroscope The fourth output of the at least one of the second data exceeding the predetermined value produces the fourth output. The method of claim 63, wherein the rotatable input mechanism is also depressible, the method further comprising: detecting a depression of one of the rotatable input mechanisms when in the low power mode; determining the rotatable input The duration of the depression of the mechanism; and exiting the low power mode based on a determination that the duration of the depression exceeds a predetermined threshold. The method of claim 70, wherein the rotatable input mechanism comprises a mechanical button, and wherein the depression represents one of pressing on the mechanical button. The method of claim 70, wherein the rotatable input mechanism comprises a capacitive button, and wherein the depression represents a touch on the capacitive button. An electronic device comprising: a touch sensitive display; a battery; at least two input mechanisms; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the And configured in the memory to be executed by the one or more processors, the one or more programs comprising instructions for: receiving a first data indicating activation of one of the first input mechanisms; receiving Instructing a second data source to be activated by one of the second input means, wherein the second data is received during a predetermined time period from receiving the first data; and in response to receiving the first data and the second data: determining Displaying the remaining amount of time after the amount of power of one of the batteries reaches a first threshold, displaying a visual cues for invoking a low power mode, detecting one of the visual cues, and responding Upon detecting the selection, the low power mode is entered. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising one or more of an electronic device having a touch sensitive display, a battery, and at least two input mechanisms When executed by the plurality of processors, causing the electronic device to: receive a first data indicating that one of the first input mechanisms is activated; Receiving a second data indicating that one of the second input mechanisms is activated, wherein the second data is received during a predetermined period of time from receiving the first data; and in response to receiving the first data and the second data: Determining a remaining amount of time before one of the batteries reaches a first threshold, displaying the remaining amount of time, displaying a visual cues for invoking a low power mode, detecting one of the visual cues, and In response to detecting the selection, the low power mode is entered. An electronic device comprising: a touch sensitive display; a battery; at least two input mechanisms; means for receiving a first data indicating activation of one of the first input mechanisms; and means for receiving a second input mechanism a component of the activated second data, wherein the second data is received during a predetermined duration from receiving the first data; and in response to receiving the first data and the second data: a means for displaying a remaining amount of time before one of the batteries reaches a first threshold value, for displaying a component for invoking a visual cues of a low power mode for detecting A component selected by one of the visual cues is measured, and means for entering the low power mode in response to detecting the selection. An electronic device comprising: a touch sensitive display; a battery; at least two input mechanisms; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be configured by the one or more The processor executes, the one or more programs comprising instructions for performing the method of any one of claims 61 to 72. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising one or more of an electronic device having a touch sensitive display, a battery, and at least two input mechanisms When executed by a plurality of processors, the electronic device is caused to execute an instruction of the method of any one of claims 61 to 72. An electronic device comprising: a touch sensitive display; a battery; at least two input mechanisms; and means for performing the method of any one of claims 61 to 72. An electronic device comprising: a touch sensitive display unit; a battery unit; at least two input mechanism units; and a processing unit coupled to the touch sensitive display unit, the battery unit and the at least two An input mechanism unit configured to: receive a first data indicating activation of one of the first input mechanism units; receive a second data indicating activation of one of the second input mechanism units, wherein the Receiving the second data within one of the predetermined periods of time; and Responding to receiving the first data and the second data: determining a remaining amount of time before one of the battery cells reaches a first threshold, enabling display of the remaining amount of time, enabling for invoking a low power One of the modes displays a visual cue, detects one of the visual cue selections, and enters the low power mode in response to detecting the selection. The electronic device of claim 79, wherein the processing unit is further configured to: in response to detecting the selection: enabling display of the device in one of the low power modes, and enabling display for a time. The electronic device of claim 79 or 80, wherein the electronic device further comprises at least one hardware button unit and a rotatable input mechanism unit, wherein the electronic device is configured to respond to when in a normal power mode Generating a first output at a touch sensitive display unit, generating a second output in response to input at the at least one hardware button unit, and generating an output in response to input at the rotatable input mechanism unit a third output, and wherein the processing unit is further configured to: determine, according to the determination that the battery power is at or below the first threshold: entering a low power mode, the low power mode is characterized by A fourth output is generated at an input at the touch sensitive display unit, the at least one hardware button unit, or the rotatable input mechanism unit. The electronic device of claim 81, wherein the fourth output is different from the first output, the second output, and the third output. The electronic device of claim 81, wherein the fourth output comprises the current time at the touch Display on the sensitive display unit. The electronic device of claim 81, wherein the fourth output comprises one of the battery levels of the battery unit indicating a display on the touch-sensitive display unit. The electronic device of claim 81, wherein the electronic device further comprises at least one of an accelerometer unit and a gyroscope unit. The electronic device of claim 85, wherein the processing unit is further configured to: receive the first data from the accelerometer unit and the at least one of the gyroscope units when in the normal power mode; and And generating a fifth output based on a determination that the first data of the at least one of the accelerometer unit and the gyro unit exceeds a predetermined value. The electronic device of claim 86, wherein the processing unit is further configured to: receive the second data from the accelerometer unit and the at least one of the gyroscope units when in the low power mode; The fourth output is generated based on a determination that the second data from the at least one of the accelerometer unit and the gyro unit exceeds the predetermined value. The electronic device of claim 81, wherein the rotatable input mechanism unit is also depressible, and wherein the processing unit is further configured to: detect the rotatable input mechanism unit when in the low power mode Depressing one of the depressions; determining a duration of the depression of the rotatable input mechanism unit; and exiting the low power mode based on a determination that the duration of the depression exceeds a predetermined threshold. The electronic device of claim 88, wherein the rotatable input mechanism unit comprises a mechanical button unit, and wherein the depression represents one of the mechanical button units Pressure. The electronic device of claim 88, wherein the rotatable input mechanism unit comprises a capacitive button unit, and wherein the depression represents a touch on the capacitive button unit.