Method for power saving in mobile devices by optimizing wakelocks
First Claim
Patent Images
1. A mobile device comprising:
- a display screen;
a memory, and a processor, the mobile device configured to;
acquire a system wakelock in response to an application wakelock acquisition request;
detect an activity state of the mobile device based on a status of the display screen;
enter a power optimization state based on the detected activity state;
release the system wakelock upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the criticality is characterized on an application-by-application basis;
acquire, while in the power optimization state, the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device, wherein to acquire the system wakelock is based on the characterized criticality.
2 Assignments
0 Petitions
Accused Products
Abstract
A method for conserving device and/or network resources is provided herein. The method includes detecting a wakelock operating on a mobile device and determining a consumption of one of a power or radio usage attributed to the detected wakelock. The method further includes determining a criticality related to user experience for the detected wakelock and releasing the detected wakelock based on the determined consumption and criticality. Related systems and mobile devices are also disclosed.
-
Citations
42 Claims
-
1. A mobile device comprising:
-
a display screen; a memory, and a processor, the mobile device configured to; acquire a system wakelock in response to an application wakelock acquisition request; detect an activity state of the mobile device based on a status of the display screen; enter a power optimization state based on the detected activity state; release the system wakelock upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the criticality is characterized on an application-by-application basis; acquire, while in the power optimization state, the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device, wherein to acquire the system wakelock is based on the characterized criticality. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A method comprising:
-
acquiring a system wakelock in response to an application wakelock acquisition request on a mobile device; detecting an activity state of the mobile device based on a status of a display screen of the mobile device; entering a power optimization state based on the detected activity state; releasing the system wakelock upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the criticality is characterized on an application-by-application basis; acquiring, while in the power optimization state, the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device, wherein acquiring the system wakelock is based on the characterized criticality. - View Dependent Claims (19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34)
-
-
35. A mobile device comprising:
-
a display screen; a memory, and a processor, the mobile device configured to; determine a criticality of applications executing on the mobile device, wherein the criticality is determined on an application-by-application basis; acquire a system wakelock in response to an application wakelock acquisition request for the application; detect an activity state of the mobile device based on a status of the display screen, wherein the status of the display screen includes whether the screen is on; enter a power optimization state based on the detected activity state; while in the power optimization state; release the system wakelock upon entering the power optimization state when the application that made the acquisition request is not critical, wherein a subsequent wakelock acquisition request by the application does not cause acquisition of the system wakelock and the system wakelock remains released unless a subsequent wakelock acquisition request is by a critical application; acquire the system wakelock in response to a subsequent wakelock acquisition request from a critical application on the mobile device. - View Dependent Claims (36, 37, 38, 39, 40, 41, 42)
-
Specification