| a93542f9d341897f3206f775fd5720663b17504f |
|
04-Feb-2016 |
Amith Yamasani <yamasani@google.com> |
Rewrite app standby stats
Don't mix up with usage stats. Keep a separate db and history
based on elapsed time and screen on time.
Unit tests for AppIdleHistory class.
Bug: 26989006
Change-Id: If343785b46da1db67f7c1c1263854c2732a232c6
/frameworks/base/core/java/android/app/usage/UsageStats.java
|
| b2d3ffaa208e341b67285e761e58ea39df89f906 |
|
27-Jan-2016 |
Adam Lesinski <adamlesinski@google.com> |
Don't change screen on time on time changes
Screen on time should be measured in elapsed realtime, not wallclock.
Cause a checkIdleStates to occur when reloading stats
(on rollover and on time change).
When time changes occur in the negative direction, the new stats file
we create can overlap the previous one with regards to its end timestamp.
Use the begin timestamp to determine which of the latest stats to merge.
(b/22716352)
Bug: 26488100
Change-Id: If31b29bbbee9e98401205b5e26bce86e181286e7
/frameworks/base/core/java/android/app/usage/UsageStats.java
|
| c8e8729244d75584ce71a74d29c452fe538a22c5 |
|
11-Jun-2015 |
Adam Lesinski <adamlesinski@google.com> |
UsageStats: Change INTERACTION to SYSTEM_INTERACTION
SYSTEM_INTERACTION events are signals to the system for a package's
implicit actions (service bound, etc).
These should not affect the API visible stats like lastTimeUsed, etc.
USER_INTERACTION is for user initiated actions (notification interaction, etc).
Bug:21761781
Change-Id: I4585cf35fbb158612a3c737710108bec34e89183
/frameworks/base/core/java/android/app/usage/UsageStats.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/UsageStats.java
|
| cc562a811da508b275254f275d6e0c1758a47d07 |
|
27-Aug-2014 |
Adam Lesinski <adamlesinski@google.com> |
Make UsageStats API comply with API Council
- Fix documentation to mention units of time in APIs.
- Return a Map instead of an ArrayMap
Bug:17289531
Change-Id: I0a2cfdc0bc003eeeb65a16e37bb7b991624b2853
/frameworks/base/core/java/android/app/usage/UsageStats.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/UsageStats.java
|
| 09a65601b24b77b7e5b3d2d4c7c30eded1ba1040 |
|
21-Jul-2014 |
Adam Powell <adamp@google.com> |
Sort ResolverActivity items based on UsageStats
Sort targets by the total amount of time the user has spent with their
containing package in the foreground.
Bug 15694906
Change-Id: I63c956424f78eb22911517674dfefd96901d19f8
/frameworks/base/core/java/android/app/usage/UsageStats.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/UsageStats.java
|