Source: https://patents.google.com/patent/EP3149501B1/en
Timestamp: 2020-01-19 23:08:52
Document Index: 304843182

Matched Legal Cases: ['Application No. 11', 'Application No. 10', 'Application No. 10', 'Application No. 11', 'Application No. 11', 'Application No. 11', 'Application No. 11', 'Application No. 11', 'Application No. 11', 'Application No. 60', 'Application No. 11']

EP3149501B1 - Battery usage tracking user interface - Google Patents
Battery usage tracking user interface Download PDF
EP3149501B1
EP3149501B1 EP14790403.1A EP14790403A EP3149501B1 EP 3149501 B1 EP3149501 B1 EP 3149501B1 EP 14790403 A EP14790403 A EP 14790403A EP 3149501 B1 EP3149501 B1 EP 3149501B1
EP14790403.1A
EP3149501A1 (en
Albert S. LIU
2014-05-30 Priority to US201462006029P priority Critical
2014-09-30 Priority to PCT/US2014/058466 priority patent/WO2015183336A1/en
2017-04-05 Publication of EP3149501A1 publication Critical patent/EP3149501A1/en
2018-11-14 Publication of EP3149501B1 publication Critical patent/EP3149501B1/en
The present disclosure relates generally to computer user interfaces for battery- powered devices, and more specifically to a user interface for tracking battery usage by software application.
In recent years, portable electronic devices such as cellular phones, tablet computers, and laptop computers have increasingly become multifunctional devices, largely driven by their ability to support a wide range of software applications. Moreover, such devices typically rely on rechargeable batteries to power the hardware and software systems that support the operation of such applications. As these devices become more fundamentally integrated into the daily routine of users, tracking of battery usage to better understand battery-consumption and optimize device use times has become increasingly important.
US2011/001457 discloses an indicator device for displaying a battery charge status of an electronic battery powered user terminal device, which is adapted to provide a plurality of applications to a user.
US2009/287433 discloses system and methods to determine the energy consumption per event type from usage data of portable devices are described.
US2011/071780 discloses a portable device including functionality to calculate battery usage and display an indication of likely battery lifespan.
The papers "Carat: Collaborative Energy Diagnosis for Mobile Devices", SENSYS'13, 11 November 2013, XP055196339 and "How Carat affects user behaviour", Human Factors in Computing Systems, ACM, 26 April 2014, XP058046802 disclose a computer system which identifies tasks which may be bugs or hogs and offers a user the chance to kill or restart those tasks
US2011/301890 discloses a system to gather batter life data form a number of mobile devices and report an aggregate indication based on one or more characteristics of the devices.
While these devices may provide interfaces for monitoring overall remaining battery life and, in some cases, for monitoring additional details such as time-of-use since the battery was last charged, such limited interfaces would not provide a user with the ability to track battery usage in relation to particularly software applications- and therefore the particular functions- that are being used on the device. Such interfaces also cannot provide recommendations for further conserving battery power based on patterns of device usage, particularly from an application-based perspective.
Accordingly, there is a need for additional tracking information with respect to battery usage on their device, such as information relating battery usage more directly to the functions that the user may employ most. The devices, methods, and interfaces described herein address the issues described above and reduce the cognitive burden on a user, produce a more efficient human-machine interface,
According to an aspect of the invention, a method of determining exceptional battery usage comprises: at an electronic device with one or more processors and memory: determining battery usage attributed to a first application over a first time period, wherein the battery usage attributed to the first application over the first time period includes exceptional battery usage that occurred during the first time period; receiving a request to display a battery usage user interface; and in response to receiving the request: in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period meets qualifier display criteria, displaying a representation of battery usage attributed to the first application over the first time period that includes qualifier information that is indicative of one or more causes of the exceptional battery usage attributed to the first application over the first time period; and in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period does not meet the qualifier display criteria, displaying a representation of battery usage attributed to the first application over the first time period that does not include the qualifier information.
FIGs. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.
FIG. 5A illustrates an exemplary user interface for navigating to a battery usage user interface.
FIG. 5B illustrates an exemplary battery usage user interface.
FIG. 5C illustrates an exemplary battery usage user interface for displaying battery usage over a period of time of device operation.
FIG. 5D illustrates yet another exemplary battery usage user interface.
FIG. 5E illustrates a battery usage histogram user interface.
FIG. 6 illustrates an exemplary user interface for adopting an enable auto-lock battery savings suggestion on a device.
FIG. 7 illustrates an exemplary user interface for adopting an enable auto-brightness battery savings suggestion on a device.
FIG. 8 is a flow diagram illustrating a method for tracking battery usage.
FIG. 9 is a flow diagram illustrating a method for tracking battery usage.
FIG. 10 is a flow diagram illustrating a method for tracking battery usage.
As discussed above, tracking of battery usage to better understand battery-consumption and optimize device use times has become increasingly important. It is desirable to provide an improved interface for tracking of battery usage, such as usage attributable to specific hardware and/or software subsystems, thereby allowing a user to quickly and efficiently monitor and conserve power and increase the time between battery charges.
Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for tracking of battery usage. FIGS. 5A-7 illustrate exemplary user interfaces for tracking of battery usage. The user interfaces in the figures are also used to illustrate the processes described below, including the processes in FIGS. 8-10.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. Patent Application 11/322,549 , "Unlocking a Device by Performing Gestures on an Unlock Image," filed December 23, 2005, U.S. Pat. No. 7,657,849 . A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
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 technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: 6,323,846 (Westerman et al. ), 6,570,557 (Westerman et al. ), and/or 6,677,932 (Westerman ), and/or U.S. Patent Publication 2002/0015024A1 . However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. Patent Application No. 11/381,313 , "Multipoint Touch Surface Controller," filed May 2, 2006; (2) U.S. Patent Application No. 10/840,862 , "Multipoint Touchscreen," filed May 6, 2004; (3) U.S. Patent Application No. 10/903,964 , "Gestures For Touch Sensitive Input Devices," filed July 30, 2004; (4) U.S. Patent Application No. 11/048,264 , "Gestures For Touch Sensitive Input Devices," filed January 31, 2005; (5) U.S. Patent Application No. 11/038,590 , "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices," filed January 18, 2005; (6) U.S. Patent Application No. 11/228,758 , "Virtual Input Device Placement On A Touch Screen User Interface," filed September 16, 2005; (7) U.S. Patent Application No. 11/228,700 , "Operation Of A Computer With A Touch Screen Interface," filed September 16, 2005; (8) U.S. Patent Application No. 11/228,737 , "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," filed September 16, 2005; and (9) U.S. Patent Application No. 11/367,749 , "Multi-Functional Hand-Held Device," filed March 3, 2006.
Device 100 may also include one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 may perform as described in U.S. Patent Application Nos. 11/241,839 , "Proximity Detector In Handheld Device"; 11/240,788 , "Proximity Detector In Handheld Device"; 11/620,702 , "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11/586,862 , "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11/638,251 , "Methods And Systems For Automatic Configuration Of Peripherals." In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).
Device 100 may also include one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 may be coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059 , "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Publication No. 20060017692 , "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer." In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term "graphics" includes any object that can be displayed to a user, including ,without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562 , "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11/968,067 , "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007.
Each of the above-identified elements in FIG. 3 may be stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures ,or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures identified above. Furthermore, memory 370 may store additional modules and data structures not described above.
∘ Icon 416 for telephone module 138, labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
∘ Icon 418 for e-mail client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread e-mails;
∘ Icon 420 for browser module 147, labeled "Browser;" and
∘ Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled "iPod;" and
∘ Icon 424 for IM module 141, labeled "Messages;"
∘ Icon 426 for calendar module 148, labeled "Calendar;"
∘ Icon 428 for image management module 144, labeled "Photos;"
∘ Icon 430 for camera module 143, labeled "Camera;"
∘ Icon 432 for online video module 155, labeled "Online Video;"
∘ Icon 434 for stocks widget 149-2, labeled "Stocks;"
∘ Icon 436 for map module 154, labeled "Maps;"
∘ Icon 438 for weather widget 149-1, labeled "Weather;"
∘ Icon 440 for alarm clock widget 149-4, labeled "Clock;"
∘ Icon 442 for workout support module 142, labeled "Workout Support;"
∘ Icon 444 for notes module 153, labeled "Notes;" and
∘ Icon 446 for a settings application or module, labeled "Settings," which provides access to settings for device 100 and its various applications 136.
It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 may optionally be labeled "Music" or "Music Player." Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
As used here, the term "affordance" refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance.
As used herein, the term "focus selector" refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a "focus selector" so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a "focus selector" so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed "jitter," where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "up stroke" of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the term "open application" or "executing application" refers to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application may be any one of the following types of applications:
3. User Interfaces And Associated Processes
FIGS. 5A-5E illustrate exemplary user interfaces for representing and tracking battery usage of a device. The user interfaces in these figures are used to illustrate the processes described below, including the processes described below with reference to FIGS. 8-10.
FIG. 5A illustrates an exemplary user interface for navigating to a battery usage user interface. User interface 500 can be displayed on a touch-sensitive display of a device (e.g., touch-sensitive display system 112 of device 100) and can responsive to gestures on a touch-sensitive surface. In some embodiments, the display and touch sensitive surface can be separate elements and in other embodiments, the display and touch sensitive surface can be a display with a touch sensitive surface (e.g., touch-sensitive display system 112 of device 100). User interface 500 can includes a general settings page with various user interface elements for accessing information about and settings for the device. For examples, as illustrated in FIG. 5A, user interface 500 includes user interface elements for information about the device ("About") and device software ("Software Update"). User interface 500 can also include user interface elements for information and settings about a voice assistant ("Siri"), search utility ("Spotlight Search"), text size of the device ("Text Size"), various accessibility features ("Accessibility"), and a background application refresh utility ("Background App Refresh"). The user interface 500 can also include a user interface element 501 for accessing battery usage of the device ("Battery Usage"). The user interface element 501 can include an indicator, such as arrow 503, to indicate to the user that activating the user interface element 501 causes navigation to another user interface. A gesture, such as a tap gesture, can be detected on touch sensitive surface 451 at user interface element 501 for battery usage of the device to navigate to the battery usage user interface.
FIG. 5B illustrates an exemplary battery usage user interface 510 that may be displayed in response to a gesture on interface element 501 of FIG. 5A. Battery usage user interface 510 includes a plurality of sections and a plurality of user interface elements, such as a section 512 corresponding to usage statistics since a last full charge ("TIME SINCE LAST FULL CHARGE"), a section 514 corresponding to suggestions to improve battery life ("BATTERY LIFE SUGGESTIONS"), and a section 516 corresponding to battery usage attributed to various items ("BATTERY USAGE"), such as various software applications. Section 512 includes a representation 512-1 of the amount of time the device has been awake and in use (e.g. making a call, using email, listening to music, browsing the web, sending and receiving text messages, or during certain background tasks such as auto-checking email, etc.) since the last full charge ("Usage") and a representation 512-2 of the amount of time the device has been powered on including the time the device has been asleep ("Standby").
Attention is now directed to section 516 of user interface 510, which provides information regarding battery usage attributed to various items, such as software applications. Section 516 includes user interface element 516-1 for selecting display of battery usage over a first time period ("Last 24 Hours," as shown) and a user interface element 516-2 for selecting display of batter usage over a second time period ("Last 7 Days," as shown). In some embodiments, battery usage is displayed for a time period that is based on a period of operation of the device, such as the last 24 hours of device operation or state (e.g., standby), even when those 24 operating hours span a calendar period of several days. In other embodiments, battery usage is displayed for a time period that is based on calendar days, irrespective of device operation or state.
In some embodiments, a selected time period (e.g., 24 hours) is designated as the default time period shown, when user interface 510 is generated in response to a request to display a battery usage user interface. In embodiments having a default time period designated for display, display of battery usage for a non-default time period (e.g., 7 days) may be requested by selecting a user interface element, such as element 516-2. In FIG. 5B, battery usage is currently shown for the last 24 hours, as indicated by the bolding of user interface element 516-1. In the exemplary interface of FIG. 5B, tracked battery usage is shown for five items as percentages of total usage: Phone application 516-3 (40%), Camera application 516-4 (25%), Maps application 516-5 (20%), Mail application 516-6 (14%), and Music application 516-7 (1%). As shown, the items are ordered by decreasing percentage of battery usage. In other embodiments, displayed items may be ordered or sorted according alternative orders such as alphabetical order, most recent usage, or the like. In FIG. 5B, battery usage for each item is shown as a percentage of the battery usage for the selected time interval (e.g., 24 hours), with 100% of the battery usage for the device attributable to the five items shown. In other embodiments, battery usage for an item may be shown in alternative formats such as a fraction of total usage, as an absolute value (e.g., amps or milliamps), or the like. The sum of the battery usage of the items shown may be less than 100% in other embodiments. Alternative embodiments of battery usage section 516 may display only items meeting certain criteria, such as items having usage that exceeds a certain threshold (e.g., greater than 1%). In some embodiments, additional items may be accessible by scrolling the screen, selecting a provided interface object, or not shown at all.
The device (e.g., device 100) may determine the battery usage value associated with each item according to a number of methods. In some embodiments, device 100 continuously or periodically monitors battery usage by one or more hardware subsystems/components or software subsystems/components, such as those shown in FIG. 3. For example, device 100 may monitor power drawn by display system 112 (e.g., from a display backlight), processor(s) 120 (e.g., a central processor or a graphics processor), a wireless antenna, a software extension associated with an active application, or a daemon (e.g., a notification daemon) running on device 100. In one embodiment, all battery usage occurring while an application (e.g., phone application 516-3) is active is attributed to that application. If a second application (e.g., camera application 516-4) becomes active on device 100, battery usage occurring during the period of activity of the second application is attributed to that application. In another embodiment, battery usage by a given subsystem (e.g., processor(s) 120) may be attributed to active and background applications according to a distributed model. For example, a percentage (e.g., 60%) of processor battery usage, resulting from execution of a first operating system process, may be attributed to an active application (e.g., phone application 516-3) while a second percentage (e.g., 40%) of processor battery usage is attributed to background processes/activity associated with another application (e.g., mail application 516-6). In some embodiments, battery usage associated with selected hardware or software subsystems is excluded from monitoring or excluded from the calculation of total battery usage. For example, battery usage associated with baseline, operating system functions may be excluded from the calculation of total battery usage such that calculated and/or displayed battery usage is only based on usage attributed to selected (e.g., discretionary) items, such as an active software application (e.g., phone application 516-3). In other embodiments, battery usage resulting from system processes and activities that primarily benefit an application (e.g., mail application 516-6) are attributed to the application, even if the application is not the active application when battery usage occurs. For example, battery usage resulting from pulling mail messages may include waking up a wireless antenna and connecting to a mail server is attributed to the mail application even if the mail application was not active/open during the battery usage. In some embodiments battery usage caused by background activity for the benefit of the second application is similarly attributed to the second application.
By monitoring, attributing, and displaying battery usage according to designated items, particular software applications, device 100 provides the information in a more salient format, more closely linked to particular function and uses of the device. Users can more readily connect the information to their use of the device and its functions and, should they desire, adjust their use to conserve battery life.
In some embodiments, device 100 monitors and logs battery usage, but does not calculate and/or attribute battery usage values until a request for display of a battery usage interface (e.g., interface 510) is received by device 100. In other embodiments, battery usage values are calculated on a continuous or periodic basis, independent of requests for display of a battery usage interface (e.g., interface 510). In some embodiments, such as the embodiment of FIG. 5B, battery usage information is specifically not attributed and displayed directly to hardware subsystems. In such embodiments, items associated with battery usage may be limited to software applications and all monitored batter usage from hardware subsystems is attributed to, and distributed between, to those software applications.
Battery usage attributed to one or more items may be displayed with qualifier information. As seen in FIG. 5B, battery usage attributed to maps application 516-5 is displayed with the qualifier "Location." Similarly, battery usage attributed to Mail application 516-6 is displayed with qualifier "Background Activity." Through the use of qualifiers, device 100 may provide the user with additional information to signal exceptional, atypical, or notable battery usage scenarios that may be relevant to the user's use patterns for an application or impact battery life for the device. Device 100 may display one or more qualifiers with battery usage information for an item based on a determination that qualifier display criteria are met and not display such qualifiers when the criteria are not met. Qualifier criteria may include, but is not limited to, criteria relating to comparative battery usage statistics, both within the set of battery usage statistics attributable to a particular item (e.g., software application) and to the device as a whole. For example, criteria may include a percentage of battery usage attributable to a particular item from a particular subsystem (e.g., wireless antenna) exceeding a minimum threshold (e.g., 30%) of total battery usage of the device or attributable to the particular item alone. With reference to the qualifier "Location" displayed with maps application 516-5, the criteria may be battery usage associated with one or more location-affiliated hardware subsystems attributable to the map application exceeding 30% of total battery usage associated with the maps application and also exceeding 1% of total battery usage across the device for the relevant time period. Similarly, qualifier "background activity" may be displayed with mail application 516-6 when software and hardware subsystems attributable to the mail application, while running in a background state, exceed 30% of total battery usage associated with the mail application and also exceeds at 1% of total battery usage across the device for the relevant time period. Other qualifier criteria may include, but is not limited to, application status (e.g., background or foreground/active), discretionary settings (e.g., high brightness), network/environmental factors such as poor network or cellular signal causing higher-than-usual battery usage from antennas, specific application extensions such as AirPlay and AirDrop extensions provided by Apple Inc., time of usage (e.g., time of day or minutes of consecutive usage). Note that, depending on the qualifier criteria and the pattern of battery usage, a qualifier may be displayed when usage is displayed according to a first time period (e.g., "Last 24 Hours"), but not displayed when a second time period is displayed (e.g., "Last 7 Days"). Accordingly, in some embodiments, even though a qualifier is displayed for the first time period, the qualifier is not necessarily also displayed for a second time period if the exceptional battery usage during the second period does not meet the qualifier display criteria. In some embodiments, the qualifier display criteria are set at a level that generally results in a minimal use of qualifiers in the battery usage interface so as to draw the user's attention to exceptional use that might be surprising to the user without cluttering the user interface with qualifiers that the user is not concerned with. This may achieved, for example, by setting a maximum number of qualifiers that can be displayed in conjunction with the use of additional criteria (e.g., total battery usage) for selecting qualifiers for display when the maximum number of criteria is exceeded. In some embodiments, multiple qualifiers may be displayed for a single item. In one embodiment where multiple qualifiers are identified for display, device 100 provides a single, aggregate qualifier based on the multiple identified qualifiers. For example, device 100 may determine that the separate qualifiers "Background Activity" and "Location" are applicable to the battery usage attributed to a software application and then aggregate the two qualifiers to display "Background Location." In another embodiment, one or more elements of multiple qualifiers may be truncated. For example, device 100 may determine that the separate qualifiers "poor cellular signal" and "audio" are applicable to the battery usage attributed to a software application and then truncate the first qualifier to display "poor cellular, audio," thereby reducing screen clutter. In another embodiment, device 100 may have logic governing or suppressing the display of multiple qualifiers, based on relationships between the qualifiers. Device 100 may determine that the separate qualifiers "location" and "antenna" are applicable to the battery usage attributed to a software application and then truncate the "antenna" qualifier to display just "location," because a user would understand that "location" services make extensive use of antennas.
FIG. 5C illustrates another exemplary battery usage user interface 520 that may be displayed in response to a gesture on interface element 501 of FIG. 5A. Section 521 of user interface 520 provides information regarding battery usage attributed to various items. In the embodiment of FIG. 5C, battery usage defaults to display for usage over a time period that is based on the period of operation of the device. The embodiment of FIG. 5C may be particularly useful, for example, during a period of initial operation of a device (e.g., a newly activated device). As operation of the device continues and exceeds certain time thresholds, the battery usage user interface may display interface options for additional time periods (or default to alternative time periods), as seen in FIG. 5B.
FIG. 5D illustrates yet another exemplary battery usage user interface 530. Interface 530 is primarily dedicated to section 531, provides information regarding battery usage attributed to various items. In some embodiments, user interface 530 may be displayed directly in response to a gesture on interface element 501 of FIG. 5A. In other embodiments, user interface 530 is displayed in response to a request to display an expanded section 531, starting from an interface having a smaller section for providing information regarding battery usage attributed to various items. As seen in FIG. 5D, battery usage resulting from a hardware or software subsystem common to several applications may aggregated and then attributed as a separate item, while not attributing that battery usage to the several applications. For example, a battery usage interface (e.g., interfaces 510, 520, or 530) may include a separate item 532-1, and associated battery usage, for "no cellular signal," (i.e., battery usage primarily resulting from a high level of cellular antennae activity due to the absence of a cellular reception) without attributing that battery usage, in whole or in part, to several applications that commonly require cellular signal. Similarly, battery usage from a software subsystem (e.g., a software personal assistant subsystem or one or more software subsystems associated with a home screen, a lock screen, or a notification screen) that may be commonly used by several applications may be included as a separate item, with associated battery usage, in a battery usage interface, without attributing battery usage from the software subsystem, in whole or in part, to several applications that commonly use the software subsystem.
FIG. 5E illustrates a battery usage histogram user interface 540 that may be displayed directly in response to a gesture on interface element 501 of FIG. 5A or in response to a request received while displaying any of interfaces 5B to 5D. User interface 540 displays changes in battery percentage (e.g., usage and charging) as a function of time.
Attention is now directed back to FIG. 5B, and to section 514 of user interface 510, in particular. Section 514 provides recommendations of actions (e.g., enabling options such as auto-lock or auto-brightness) or settings that may be used to improve battery life. In some embodiments, section 514 or particular suggestions of section 514 are displayed only in response to a determination that battery savings suggestion criteria have been met and are not displayed when such criteria are not met. For example, a suggestion to enable auto-lock (514-1) may only be displayed if device 100 determines, based on historical battery usage, that enabling auto-lock would improve battery usage, with or without a minimum improvement threshold value (e.g., at 1%, 2%, or 5%). Similarly, a suggestion to enable auto-brightness (514-2) may only be displayed if device 100 determine, based on historical battery usage, that enabling auto-brightness would improve battery usage. Upon receiving an input on a battery savings suggestion, device 100 may provide the user with an interface for adopting the battery savings suggestion. In other embodiments, battery savings suggestions may include suggestions to enable or disable wireless connectivity or a cellular protocol (e.g., LTE), and configure application parameters (e.g., mail fetch parameters). In one embodiment, device 100 monitors and logs or records one or more device operational parameters to determine whether a battery savings suggestion criteria would be met. For example, device 100 may log or record ambient light values to determine if enabling auto-brightness would result in a predicted improvement in battery usage.
FIG. 6 illustrates an exemplary user interface 600 for adopting an enable auto-lock battery savings suggestion on device 100. In some embodiments, the user interface of FIG. 6 is a user interface also accessible from a settings option or application of device 100. In other embodiments, the user interface of FIG. 6 is specially provided in response to a request made from a battery usage interface. Similarly, FIG. 7 illustrates an exemplary user interface 700 for adopting an enable auto-brightness battery savings suggestion on device 100.
FIG. 8 is a flow diagram illustrating process 800 for tracking battery usage. Process 800 may be performed at an electronic device with one or more processors and memory, like device 100 (FIGS. 1A-1B) and device 300 (FIG. 3). At block 802, the device attributes a portion of battery usage of a first hardware subsystem to a first application based on the battery usage of the first hardware subsystem that occurred during activity by the first application. At block 804, the device attributes a portion of the battery usage of the first hardware subsystem to a second application based on the battery usage of the first hardware subsystem that occurred during activity by the second application. Optionally, at block 804, the device may attribute a portion of battery usage of a second hardware subsystem to the first application based on the battery usage of the second hardware subsystem that occurred during activity by the first application and attribute a portion of the battery usage of the second hardware subsystem to the second application based on the battery usage of the second hardware subsystem that occurred during activity by the second application. Optionally, at block 804, the device may attribute a portion of battery usage of a first software subsystem to the first application based on the battery usage of the first software subsystem that occurred during activity by the first application and attribute a portion of the battery usage of the first software subsystem to the second application based on the battery usage of the first software subsystem that occurred during activity by the second application. At block 806, the device receives a request (e.g., request received in interface of FIG. 5A) to display a battery usage user interface. At block 808, in response to the request, the device displays the battery usage user interface (e.g., FIG. 5A-5E) that includes a representation of the battery usage attributed to the first application and a representation of the battery usage attributed the second application.
Note that details of the processes described above with respect to process 800 (e.g., FIG. 8) are also applicable in an analogous manner to the processes described below. For example, processes 900 and 1000 may include one or more of the characteristics of the various processes described above with reference to process 800. For brevity, these details are not repeated above. The various methods and techniques described above with reference to process 800 may be optionally implemented as one or more units, such as those described with regard to FIG. 11.
The operations described above with reference to the figures may be implemented by components depicted in FIGS. 1A-1B. For example, attribution operations, request operations, and display operations may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.
FIG. 9 is a flow diagram illustrating method 900 for tracking battery usage. Method 900 may be performed at an electronic device with one or more processors and memory, like device 100 (FIGS. 1A-1B) and device 300 (FIG. 3). At block 902, the device determines battery usage attributed to a first application over a first time period. The battery usage attributed to the first application over the first time period includes exceptional battery usage that occurred during the first time period. At block 904, the device receives a request to display a battery usage user interface (e.g., request received in interface of FIG. 5A). At block 906, in response to receiving the request, and in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period meets qualifier display criteria, the device displays a representation of battery usage (e.g., FIG. 5A-5E) attributed to the first application over the first time period that includes qualifier information that is indicative of one or more causes of the exceptional battery usage attributed to the first application over the first time period. At block 908, in response to receiving the request, and in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period does not meet the qualifier display criteria, displaying a representation of battery usage (e.g., FIG. 5A-5E, without qualifiers) attributed to the first application over the first time period that does not include the qualifier information.
Note that details of the processes described above with respect to process 900 (e.g., FIG. 9) are also applicable in an analogous manner to the processes described below. For example, processes 800 and 1000 may include one or more of the characteristics of the various processes described above with reference to process 900. For brevity, these details are not repeated above. The various methods and techniques described above with reference to process 900 may be optionally implemented as one or more units, such as those described with regard to FIG. 11.
The operations described above with reference to the figures may be implemented by components depicted in FIGS. 1A-1B. For example, determination operations, request operations, and display operations may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.
FIG. 10 is a flow diagram illustrating process 1000 for tracking battery usage. Process 1000 may be performed at an electronic device with one or more processors and memory, like device 100 (FIGS. 1A-1B) and device 300 (FIG. 3). At block 1002, the device receives a request to display a battery usage user interface (e.g., request received in interface of FIG. 5A). At block 1004, the device determines whether battery savings suggestion criteria have been met for a first setting. At block 1006, in response to the request, and in accordance with a determination that the battery savings suggestion criteria have been met for the first setting, the device displays a battery usage interface that includes a suggestion for adjusting the first setting (e.g., FIGs. 5A-5C). At block 1008, in response to the request, and in accordance with a determination that the battery savings suggestion criteria have not been met for the first setting, the device displays a battery usage interface (e.g., FIG. 5D) that does not include the suggestion for adjusting the first setting.
Note that details of the processes described above with respect to process 1000 (e.g., FIG. 10) are also applicable in an analogous manner to the processes described below. For example, processes 800 and 900 may include one or more of the characteristics of the various processes described above with reference to process 1000. For brevity, these details are not repeated above. The various methods and techniques described above with reference to process 1000 may be optionally implemented as one or more units, such as those described with regard to FIG. 11.
The operations described above with reference to the figures may be implemented by components depicted in FIGS. 1A-1B. For example, request operations, determination operations, and display operations may be implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B.
As shown in FIG. 11, an electronic device 1100 includes a display unit 1102 configured to display a user interface, an optional touch-sensitive surface unit 1104 configured to receive user contacts; and a processing unit 1106 coupled to the display unit 1102 and the touch-sensitive surface unit 1104. In some embodiments, the processing unit 1106 includes a display enabling unit 1108, a receiving unit 1110, a determining unit 1112, and an attributing unit 1114. The units of FIG. 11 may be used to implement the various techniques and methods described above with respect to FIGS. 5-10.
In some embodiments, the display enabling unit 1108 is configured to cause a display of a user interface (or portions of a user interface) in conjunction with the display unit 1102. For example, the display enabling unit 1108 may be used for: displaying the battery usage user interface that includes a representation of the battery usage attributed to the first application and a representation of the battery usage attributed the second application; displaying a representation of battery usage attributed to the first application over the first time period that includes qualifier information that is indicative of one or more causes of the exceptional battery usage attributed to the first application over the first time period; displaying a representation of battery usage attributed to the first application over the first time period that does not include the qualifier information; displaying a battery usage interface that includes a suggestion for adjusting the first setting; and displaying a battery usage interface that does not include the suggestion for adjusting the first setting.
In some embodiments, the receiving unit 1110 is configured to receive input. The input may be received, for example, through the use of the touch-sensitive surface unit 1104. In some embodiments, the input may be received, for example, through the use of the input/output (I/O) interface 330 shown in FIG. 3. For example, the receiving unit 1110 may be used for: receiving a request to display a battery usage user interface.
In some embodiments, the determining unit 1112 is configured to make determinations. For example, the determining unit 1112 may be used for: determining battery usage attributed to a first application over a first time period, wherein the battery usage attributed to the first application over the first time period includes exceptional battery usage that occurred during the first time period; and determining whether battery savings suggestion criteria have been met for a first setting.
In some embodiments, the attributing unit 1114 is configured to attribute information. For example, the attributing unit 1114 may be used for: attributing a portion of battery usage of a first hardware subsystem to a first application based on the battery usage of the first hardware subsystem that occurred during activity by the first application; and attributing a portion of the battery usage of the first hardware subsystem to a second application based on the battery usage of the first hardware subsystem that occurred during activity by the second application.
determining battery usage attributed to a first application over a first time period, wherein the battery usage attributed to the first application over the first time period includes exceptional battery usage that occurred during the first time period;
receiving a request to display a battery usage user interface; and
in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period meets qualifier display criteria, displaying a representation of battery usage attributed to the first application over the first time period that includes qualifier information that is indicative of one or more causes of the exceptional battery usage attributed to the first application over the first time period; and
in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the first time period does not meet the qualifier display criteria, displaying a representation of battery usage attributed to the first application over the first time period that does not include the qualifier information.
The method of claim 1, wherein the qualifier display criteria includes a criterion that is met when the exceptional battery usage is at least a threshold percentage of total battery usage attributed to the first application.
The method of claim 2, wherein the threshold percentage is one third of the total battery usage attributed to the first application.
The method of any of claims 1-3, wherein the qualifier display criteria includes at least one of a criterion that is met when the exceptional battery usage is at least a threshold percentage of total battery usage, and a criterion that is met when the exceptional battery usage was caused by one or more background processes.
determining battery usage attributed to the first application over a second time period, wherein the battery usage attributed to the first application over the second time period includes exceptional battery usage that occurred during the second time period;
receiving a request to display the battery usage user interface corresponding to the second time period; and
in response to receiving the request to display the battery usage user interface corresponding to the second time period:
in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the second time period meets qualifier display criteria, displaying a representation of battery usage attributed to the first application over the second time period that includes qualifier information that is indicative of the cause of the exceptional battery usage attributed to the first application over the second time period; and
in accordance with a determination that the exceptional battery usage attributed to the first application that occurred during the second time period does not meet the qualifier display criteria, displaying a representation of battery usage attributed to the first application over the second time period that does not include the qualifier information.
determining battery usage attributed to a second application over the first time period, wherein the battery usage attributed to the second application over the first time period includes exceptional battery usage that occurred during the first time period;
receiving a request to display the battery usage user interface; and
in accordance with a determination that the exceptional battery usage attributed to the second application that occurred during the first time period meets qualifier display criteria, displaying a representation of battery usage attributed to the second application over the first time period that includes qualifier information that is indicative of one or more causes of the exceptional battery usage attributed to the second application over the first time period; and
in accordance with a determination that the exceptional battery usage attributed to the second application that occurred during the first time period does not meet the qualifier display criteria, displaying a representation of battery usage attributed to the second application over the first time period that does not include the qualifier information.
determining battery usage attributed to the second application over a second time period, wherein the battery usage attributed to the second application over the second time period includes exceptional battery usage that occurred during the second time period;
in accordance with a determination that the exceptional battery usage attributed to the second application that occurred during the second time period meets qualifier display criteria, displaying a representation of battery usage attributed to the second application over the second time period that includes qualifier information that is indicative of the cause of the exceptional battery usage attributed to the second application over the second time period; and
in accordance with a determination that the exceptional battery usage attributed to the second application that occurred during the second time period does not meet the qualifier display criteria, displaying a representation of battery usage attributed to the second application over the second time period that does not include the qualifier information.
The method of any of claims 1-7, wherein the battery usage user interface includes representations of a plurality of applications having qualifier information.
The method of any of claims 1-8, wherein the battery usage user interface includes fewer representations of applications with qualifier information than representations of applications without qualifier information.
The method of any of claims 1-9, wherein the qualifier information displayed includes at least one of descriptions of a plurality of causes of the exceptional battery usage, descriptions of a plurality of causes of the exceptional battery usage and a description of a cause of the exceptional battery usage is truncated, and descriptions of a plurality of causes of the exceptional battery usage and a description of a cause of the exceptional battery usage is suppressed.
The method of any of claims 1-10, wherein the qualifier information displayed includes a description of one or more causes of the exceptional battery usage, the one or more causes including one or more of location determination, background activity, poor cellular signal, audio playback, antenna usage and application extension execution.
The method of claims 1-11, wherein the battery usage user interface includes a representation of battery usage attributed to at least one application that does not include qualifier information.
A non-transitory computer-readable storage medium comprising instructions for performing the method of any of claims 1-12.
a non-transitory computer-readable storage medium comprising instructions for performing the method of any of claims 1-12; and
one or more processors capable of executing the instructions of the non-transitory computer-readable storage medium.
a processor coupled to the display and the memory, the processor configured to perform the method of any of claims 1-12.
EP14790403.1A 2014-05-30 2014-09-30 Battery usage tracking user interface Active EP3149501B1 (en)
US201462006029P true 2014-05-30 2014-05-30
PCT/US2014/058466 WO2015183336A1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
EP18197727.3A EP3457152A1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
EP18197727.3A Division-Into EP3457152A1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
EP18197727.3A Division EP3457152A1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
EP3149501A1 EP3149501A1 (en) 2017-04-05
EP3149501B1 true EP3149501B1 (en) 2018-11-14
ID=51830601
EP14790403.1A Active EP3149501B1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
EP18197727.3A Pending EP3457152A1 (en) 2014-05-30 2014-09-30 Battery usage tracking user interface
US (2) US9606706B2 (en)
EP (2) EP3149501B1 (en)
TW (1) TWI575369B (en)
WO (1) WO2015183336A1 (en)
WO2019084031A1 (en) * 2017-10-23 2019-05-02 Johnson Controls Technology Company User interface for a battery tester
GB2448534B (en) 2007-04-19 2009-11-18 Vodafone Plc Mobile telecommunications device
KR101399112B1 (en) * 2012-08-31 2014-05-30 주식회사 팬택 Portable electronic device and battery management method for the device
2014-09-30 US US14/503,078 patent/US9606706B2/en active Active
2014-09-30 EP EP14790403.1A patent/EP3149501B1/en active Active
2014-09-30 WO PCT/US2014/058466 patent/WO2015183336A1/en active Application Filing
2014-09-30 EP EP18197727.3A patent/EP3457152A1/en active Pending
2014-10-08 TW TW103135094A patent/TWI575369B/en active
2017-03-07 US US15/452,536 patent/US10416745B2/en active Active
US20170177054A1 (en) 2017-06-22
US20150346933A1 (en) 2015-12-03
US10416745B2 (en) 2019-09-17
EP3149501A1 (en) 2017-04-05
TW201544949A (en) 2015-12-01
TWI575369B (en) 2017-03-21
EP3457152A1 (en) 2019-03-20
WO2015183336A1 (en) 2015-12-03
US9606706B2 (en) 2017-03-28
AU2017258967B2 (en) 2019-07-04 Devices, methods, and graphical user interfaces for interacting with a control object while dragging another object
Ipc: G06F 1/32 20060101ALI20180507BHEP
Ipc: G06F 3/041 20060101ALI20180507BHEP
Ipc: G01R 31/36 20060101AFI20180507BHEP
Ipc: G06F 1/28 20060101ALI20180507BHEP
Ipc: G06F 3/0484 20130101ALI20180507BHEP
Ref document number: 1065468
Ref document number: 602014036104