60aa35b756707a16d310c222a36edbcef9d56ed4 |
|
25-Apr-2018 |
Suprabh Shukla <suprabh@google.com> |
Using a list to store usage events Moving UsageEvent.Event objects to an array list sorted on the event timestamps as there can be multiple events with the same timestamps. Test: atest android.app.usage.EventListTest Existing tests: atest android.app.usage.cts.UsageStatsTest Bug: 74406113 Change-Id: Idc7f2a8db6e5a9499b3b0b74efbf014b17fa495f
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
3378aa9f88101d77bc52c1a00b257c752bd8c193 |
|
31-Mar-2018 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #74404949: Screen state usage API Add events for the keyguard being shown and hidden. Bug: 74404949 Test: atest CtsUsageStatsTestCases:UsageStatsTest\#testInteractiveEvents Change-Id: I038e03cf4ba80669d7d17c3d66b98ee81050abc8
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
ced54398cc0dfd2f782153560c2ffd0eb8743045 |
|
26-Feb-2018 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #74404949: Screen state usage API Add usage stats tracking of screen time. There are two new events, one for when the device is an interactive state, the other for when it is non-interactive. Also add a whole new usage stats API for retrieving aggregated data that is associated with general events, not particular packages. In this case it allows you to find the time the device spent interactive and non-interactive and the count of the transitions in to each of those states. Bug: 74404949 Test: atest CtsUsageStatsTestCases:UsageStatsTest\#testInteractiveEvents Change-Id: Ibe6d55e2aecb0c8519b1358644378ec5c7a4250d
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
bc813eb26e3027856114a26312e36e4bad86bd86 |
|
21-Mar-2018 |
Amith Yamasani <yamasani@google.com> |
Provide app launch count in UsageStats This counts the number of times the app was launched from outside the app and ignores intra-app activity transitions. Introduce a new permission for registering to observe app usage. Fixes a bug where Settings couldn't force the app into another bucket if it was recently launched. Bug: 74335821 Fixes: 76100712 Test: Manual test using Settings Test: UsageStatsTest to verify permission change Change-Id: Ibd343c1cfa37089a3ac6fc30ba3194e21a9be499
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
119be9a5fc4033eba570ec94b94862401ee84570 |
|
19-Feb-2018 |
Amith Yamasani <yamasani@google.com> |
Improve reporting of bucketing reason Keep track of main and sub reason for bucket change Bug: 73178753 Test: atest AppIdleHistoryTests Change-Id: I4936281ac06046bb5ffed9f3306efa24c7fd47ab
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
bfc4bf5febe3d97d3f51206c9ead2f7d2b05e700 |
|
19-Jan-2018 |
Amith Yamasani <yamasani@google.com> |
Keep history of standby bucket changes. Push standby bucket changes into UsageStats as events. Don't use the event for aggregation. Bug: 63527785 Test: atest CtsUsageStatsTestCases:UsageStatsTest Change-Id: Icd152b21935e3ef73aaa1a62f09574e51ce921bd
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
ad623015a119efe9b63f594af9c4703f40a0c27b |
|
15-May-2017 |
Makoto Onuki <omakoto@google.com> |
Restrict access to instant app data in usage stats - Events are obfuscated based on whether the app was instant or not at the time each event was logged. - UsageStats are obfuscated based on whether each app is instant or not at the moment. Bug 38202133 Test: Manual test using UsageStatsTest and instant apps Change-Id: I3c74309196b88d010d317cb0dd6749bf4624e876
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
53b4314ad9b43b1890cbd765b896ccb0f005fdeb |
|
14-Nov-2016 |
Kang Li <kanlig@google.com> |
Add Sharing Histories to UsageStatsManager. This CL is for Android O Smart-Sharing (b/30982298). By this CL, sharing counts are logged with UsageStatsManager. Bug: 30982298 Test: manual - shared images in Camera and texts in Chrome using a mobile device. Change-Id: I0b4aa0506f99b3083d140a48f7b4bdd5b1c5afb6
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
ac042501c816fa9a65aed005060ebdcfc0a0f3b2 |
|
21-May-2016 |
Makoto Onuki <omakoto@google.com> |
ShortcutManager: Implement usage report API Bug 28536054 Change-Id: I293e8eaad523e3b0d76d562fc381601633451ed3
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
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/services/usage/java/com/android/server/usage/UsageStatsXmlV1.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/services/usage/java/com/android/server/usage/UsageStatsXmlV1.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/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
690f78adf1737b2356d341b46f21a4e2d5df58eb |
|
27-Feb-2015 |
Edward Cunningham <ejc@google.com> |
Fix UsageStats to report correct endTime from XML Bug: 19529542 Change-Id: Iacb1a245a40c6b88ae15740797217f59d5fca1e6
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
37a46b48dcb7e34ee3669cfb2ed78af08bfca3c7 |
|
06-Sep-2014 |
Adam Lesinski <adamlesinski@google.com> |
Store time offsets for UsageStats XML This will make adjusting for time changes easier in the future. Change-Id: I49d2dda4cc6dcb1378a58c814849924f585e0417
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
7f61e96db7c90c1f4418359672aa4656aebee500 |
|
03-Sep-2014 |
Adam Lesinski <adamlesinski@google.com> |
Add Configuration changes to UsageStats Bug:17354208 Change-Id: I9b2f595e51b656607e30e798926cfb7e25134944
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|
9d9607527f5bbf49c96565b63b90e36276b0dda7 |
|
25-Aug-2014 |
Adam Lesinski <adamlesinski@google.com> |
Split up ComponentName in UsageEvents.Event Some events in the future may not have originated from a class, so we shouldn't be using ComponentName. Bug:17259858 Change-Id: Id7fe3245b91596cf27ae4ec51655602f01665622
/frameworks/base/services/usage/java/com/android/server/usage/UsageStatsXmlV1.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/services/usage/java/com/android/server/usage/UsageStatsXmlV1.java
|