| 4a503b1ece485d44c15eb02ec2bcd464b46e6f7f |
|
07-Aug-2015 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #22989030: Separate battery whitelists
We now have a new whitelist you can put apps in, which
opts them out of the old battery saver mode and new app idle,
but doesn't keep them from going in to doze. This is for a few
special cases that we had previously whitelisted for battery saver,
and inherited to the new modes... ultimately we should figure out
how to get these apps out of the whitelist completely, but this
will help for now.
Apps in this new whitelist are not shown in the UI, because they
are still significantly restricted by not being able to operate
normally in doze. This also means they are still visible in the
list of all apps for the user to be able to put them on/off the
complete whitelist if that is what they really want.
In the course of doing this, I needed to clean up code in the
network policy manager to better separate management of the
two firewall rules that now have different whitelists applied
to them. This also hopefully just generally simplifies and cleans
up that code. Hopefully!
Change-Id: I92e15f2f85899571dd8b049b5e3eb1354f55f353
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 8dca36dc8a5d17315775ce216689addc5bd9be00 |
|
19-Jun-2015 |
Xiaohui Chen <xiaohuic@google.com> |
system_server: optimize app idle parole state change
Currently when app idle parole state changes, all idle apps' states
are updated one by one including firewall modifications which are
very expensive. This optimization gets rid of individual firewall
rule changes and makes sure we only modify the firewall once at child
chain level.
BUG: 21446713
Change-Id: Iafc415fe0bc127826fe17894d4fedcf1755cb17d
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 37a40c24deb02bca3868a8085069afae112f22e4 |
|
17-Jun-2015 |
Amith Yamasani <yamasani@google.com> |
App Standby : Association between content providers and their sync adapter
Set sync adapters to active if the associated content providers are used
at foreground process state.
Minimize how frequently published content providers are reported by
keeping track of last reported time.
Also cache sync adapters associated with an authority in SyncManager.
Bug: 21785111
Change-Id: Ic2c8cb6a27f005d1a1d0aad21d36b1510160753a
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 06bf824628c118fbd5ad6756913d7fd63a6f4ce5 |
|
09-May-2015 |
Amith Yamasani <yamasani@google.com> |
Idle timebase
Use screen on time as timebase for idling out apps
that have been inactive.
Store the time when an app was last active as an additional
package state in UsageStats. Compare it to screenOnTime to decide
if it's inactive.
Exclude device idle whitelist from apps that can go inactive.
Bug: 20066058
Change-Id: I709f9f31a9affa7ca6e1ae3e4c5729c5fb221669
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| b0ff32245cb6b51e43dd3ee40b86d683c62de2b9 |
|
04-Mar-2015 |
Amith Yamasani <yamasani@google.com> |
Throttle jobs for idle apps
First pass at delaying jobs from apps that are idle.
TODO: Throttle syncs
TODO: Provide a periodic point at which apps are checked for idleness.
Apps that switch to foreground process state are tracked by UsageStats
as an INTERACTION event that affects the last-used timestamp.
JobScheduler's logic for when an app is ready is trumped by the idleness
of the app, and only if the battery is not charging. When charging state
changes, we update the idle state of all the tracked jobs.
android package is whitelisted.
Bug: 20066058
Change-Id: I0a0acb517b100a5c7b11e3f435f4141375f3451f
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 978a1ed5aa2752cd36ff51df91d2d2d8be2171d9 |
|
02-Mar-2015 |
Adam Lesinski <adamlesinski@google.com> |
Add generic "INTERACTION" event type to UsageStatsManager
This will allow for updating a package's last time used
property for packages that are interacted in ways other than
launching their activities (interacting with notifications, etc.)
Change-Id: Ic6f9519f46fa04abd37ea6fc9475bcd9ea721003
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 7f61e96db7c90c1f4418359672aa4656aebee500 |
|
03-Sep-2014 |
Adam Lesinski <adamlesinski@google.com> |
Add Configuration changes to UsageStats
Bug:17354208
Change-Id: I9b2f595e51b656607e30e798926cfb7e25134944
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 3516800b611a79339a3c188332d13a26e9086b09 |
|
22-Jul-2014 |
Adam Lesinski <adamlesinski@google.com> |
Second iteration of the UsageStats API
Based on feedback from API council, updated the API.
Also added support for querying the event log.
Change-Id: Ibaa008b9e5bd145acdfe8e20c25c2ed2d96be123
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 3c153519ca5f2b66b88901374383f943c9d77df7 |
|
24-Jul-2014 |
Adam Lesinski <adamlesinski@google.com> |
Add Per-User logging of UsageStats
Change-Id: I4518c5d3c56b3821292accb886f9fb21f3a8b25f
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|
| 0debc9aff4c0cbc28e083a948081d91b0f171319 |
|
17-Jul-2014 |
Adam Lesinski <adamlesinski@google.com> |
First iteration of a public UsageStats API
UsageStats API that allows apps to get a list of packages that have been
recently used, along with basic stats like how long they have been in
the foreground and the most recent time they were running.
Bug: 15165667
Change-Id: I2a2d1ff69bd0b5703ac3d9de1780df42ad90d439
/frameworks/base/core/java/android/app/usage/UsageStatsManagerInternal.java
|