Apple Inc.

Purdue Research Foundation

Abhinav Pathak

Amit K Vyas

Albert S Liu

Yu Charlie Hu

Anand Ramadurai

Conor J O'Reilly

Rohit Mundra

Patrick L Coffman

David S Choi

Anthony R Newnam

Anca Andreea Chandra

Drew A Schmitt

Anshul Dawra

Yue Li

Prajakta S Karandikar

Tianhe Wu

Sanket V Bedare

Abhilash Jindal

Samuel Midkiff

Chaohao Wang

Paolo Sacchetto

Jean-Pierre Simon Guillou

Patrick Y Law

Arthur L Spence

Franco Travostino

Mohammad Ali Jangda

Yifan Zhang

Michael S Ferris

Christopher Edward Glazowski

Paul M Thompson

Olivier Mardinian

Kevin C Milden

Roberto Alvarez

Henri S Berger

Matthew Smith

Daniel Lertpratchya

Shashi K Dua

Udaykumar R Raval

Sathish K Narayanaswamy

Christopher W Chaney

Vividh Siddha

Eduardo Sanchez

Vladislav Sahnovich

Daniel J Etter

Andreas C Bergen

Soren C Spies

Scott C Tooker

Christopher R D'Angelo

Hari Gorak

Sean Shi

Aditya Bhushan

Hina Dixit

Eisuke Arai

Craig Michael Federighi

Nicholas D Felton

James Michael Magee

Kartik R Venkatraman

Daniel Andreas Steffen

Ethan T Bold

Anthony J Chivetta

Han Ming Ong

Phillip J Azar

Ashish Patro

Matthew C Widmann

Gina B Lu

Brian K Tearse-Doyle

Goutham Mani

Aakriti Mittal

Arjun S Vasudevan

Nehal Bhandari

Jeffrey S Lale

Andrew P Sakai

Terrence R Long

Anand Subramanian

Vincent B Yeh

Steve Brashear

Ritika Kalia

Conor J O'REILLY

This disclosure provide various techniques for decreasing the amount of energy consumed on an electronic device by one or more background processes. By implementing a fast energy accounting engine that may quickly detect changes in energy usage by the background processes and report the changes to a dynamic activity scheduler, a system may decrease the overall energy consumed by the one or more background processes.

Fast energy accounting system

A method for generating an energy usage profile for a software program executed in a computing device includes generating a call trace of an executed system call, identifying a first power consumption and duration of a first power state due to the first system call using a model, identifying a second power consumption and duration of a second power state based on the model, and generating an energy usage profile for the software program. The energy usage profile includes energy consumption of the computing device for the system call based on the first power consumption level multiplied by the first duration and the second power consumption level multiplied by the second duration associated an identifier for the call trace.

System and method for energy usage accounting in software applications

Embodiments of the present disclosure include methods and systems for generating and processing energy consumption reports received from a plurality of devices. The reports may include a plurality of call stacks captured and stored by remote device as a result of an energy consumption of the corresponding device. For each energy consumption report, the plurality of call stacks may be analyzed to determine a representative call stack of the energy consumption report. The energy consumption reports may be assigned to one or more of a plurality of energy consumption categories based on distances between the representative call stacks of the energy consumption reports and corresponding representative call stacks of the energy consumption categories. A request may be received for energy consumption reports for a particular energy consumption category. Upon receiving the request, providing a representative set of energy consumption reports assigned to the particular energy consumption category.

Detection and analysis of energy consumption of software applications

Embodiments of the present disclosure present devices, methods, and computer readable medium for techniques for measuring operational performance metrics, and presenting these metrics through an application programming interface (API) for developers to access for optimizing their applications. Exemplary metrics can include central processing unit or graphics processing unit time, foreground/background time, networking bytes (per application), location activity, display average picture luminance, cellular networking condition, peak memory, number of logical writes, launch and resume time, frame rates, and hang time. Regional markers can also be used to measure specific metrics for in application tasks. The techniques provide multiple user interfaces to help developers recognize the important metrics to optimize the performance of their applications. The data can be normalized over various different devices having different battery size, screen size, and processing requirements. The user interfaces can provide an intelligent method for visualizing performance changes for significant changes in application versions.

Logging techniques for third party application data

In some embodiments, an electronic device displays one or more representations of power usage of the electronic device, including across various periods of time and subperiods of time within those periods. In some embodiments, the displayed information reflects power usage both for periods of the display being on and periods of the display being off. In some embodiments, the displayed information includes power usage attributed to various mobile applications running on the electronic device. In some embodiments, the electronic device displays recommendations to reduce the usage of power by the electronic device, which a user has the option of applying. In some embodiments, the electronic device displays prose insight into power usage, indicating causes of the power usage.

User interfaces for indicating battery information on an electronic device

An electronic device having a user interface for displaying battery usage of the device over a given time period. Suggestions to improve device battery life are displayed along with usage when battery savings suggestions criteria are met.

Battery usage tracking user interface

Visualization techniques for third party application data

Techniques are disclosed performing a power logging in a computer system at a sub-process level. An exemplary method includes an operating system of the computer system determining process information indicative of which sub-portions of one or more processes are running on the computer system at different points in time, as well as may determining power information for the computer system at different points in time. The operating system may the create, from the process information and the power information, a power log indicative of power usage of sub-portions of processes at a plurality of points in time. The power logging may extend to both core and non-core resources of the system. For non-core resources, the power usage may be estimated in some cases based on the type of non-core resource being called as well as parameters passed to the non-core resource.

Microprocessor power logging at a sub-process level

Circuits, methods, and apparatus that may estimate the power being consumed by an OLED display screen of an electronic device, may provide further information about that power usage, may modify or change functions performed by the electronic device based on that power usage, and may inform an application's developer about the amount of power being used by the electronic device while the electronic device is running the application. One example may estimate the power being used by an OLED display screen of an electronic device by determining the content of images being displayed during a duration. The estimated power may then be presented to a user. The estimated power may be used in decisions to modify or change parameters of the screen or other device components.

Graphically providing OLED display power modeling

Clustering techniques for third party application data

Embodiments of the present invention provide a system and methods for detecting power bugs. In one embodiment, a computer-implemented method for analyzing a computer code includes generating a control flow graph for at least a portion of the computer code at a processor. The method further includes identifying power bugs by traversing the control flow graph if the control flow graph exits without performing a function call to deactivate power to any component of a device configured to execute computer executable instructions based on the computer code after performing a function call to activate power.

Systems and methods of detecting power bugs

Some embodiments of the invention provide a novel architecture for debugging devices. This architecture includes numerous devices that without user intervention automatically detect and report bug events to a set of servers that aggregate and process the bug events. When a device detects a potential bug event, the device in some embodiments generates a description of the potential bug event, and sends the generated description to the server set through a network. In addition to generating such a description, the device in some embodiments directs one or more of its modules to gather and store a collection of one or more data sets that are relevant to the potential bug event, in case the event has to be further analyzed by the server set. In the discussion below, the generated bug-event description is referred to as the event signature, while the gathered collection of data sets for an event is referred to as the event's data archive. The server set aggregates and processes the bug-event signatures that it receives from the various devices. For only a subset of the reported bug-event signatures, the server set then directs the devices that sent these signatures to also send the data archives that these devices have gathered and stored for the events associated with these signatures. These data archives can be further analyzed to identify the root causes of the bug events.

Auto bug capture

Growing community of inventors

San Jose, CA, United States of America

Abhinav Pathak