13d875fb5225b1ca74249994784ef3fed7293e5b |
|
02-Oct-2017 |
Daniel Nishi <dhnishi@google.com> |
Fix a cache calculation regression. Cache size was being double-counted for apps in their drilldown. Change-Id: I44ec03470050dfbce392348c3336dd5e9bb54c36 Fixes: 67028136 Test: SettingsLib integ tests
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|
c260d2ebbc42159689c938ff2bf369a7dd7dd38b |
|
23-Jun-2017 |
Daniel Nishi <dhnishi@google.com> |
Add in the getCacheQuotaBytes method to wrapper. Bug: 62623731 Test: Settings Unit Test Change-Id: Ibd779c7d9e60c44440483489b231ba0715321bc1
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|
ddff807b762a8a455287abc97aea8f97b98fb104 |
|
26-May-2017 |
Jeff Sharkey <jsharkey@android.com> |
Consistent "low storage" behavior. When answering the question "how much space is free", use the same logic for Settings UI and StorageManager.getAllocatableBytes(). That is, the reported free space is usable bytes plus any cached data the system is willing to delete automatically. This does *not* include any reserved cache space, since we don't want abusive apps to penalize other well-behaved apps that are storing their data in cache locations. Callers freeing cached data need to now explicitly request defiance of the reserved cache space. (Most callers are already doing this by using FLAG_ALLOCATE_AGGRESSIVE.) Rewrite the core logic of DeviceStorageMonitorService to understand this new "reserved" cache space, and to be easier to understand. It also now handles cached data on adopted storage volumes, which had been ignored until now. Also fix bug where we had skipped "low" broadcasts when the device skipped directly from/to "full" state. Bug: 38008706 Test: cts-tradefed run commandAndExit cts-dev -m CtsJobSchedulerTestCases -t android.jobscheduler.cts.StorageConstraintTest Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest Change-Id: Icbdcf3b52775f7ada1ceaeff2f96094c8d8052f9
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|
789a8fc792725e4988ff43d554b3c8c037c41921 |
|
16-Apr-2017 |
Jeff Sharkey <jsharkey@android.com> |
Storage API polishing. Based on API council feedback, switch to using real UUID objects instead of Strings. Since UUID is a general-purpose utility class that will be passed around quite a bit, add it to Parcel and Bundle. Define well-known namespaced UUID values for "default" and "primary physical" storage devices, which will let us annotate a bunch of things with @NonNull. Define new extras for MANAGE_STORAGE intent that apps can use to signal where and how much space they'd like the user to free up. Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest Bug: 37325923, 35812899, 35806020 Change-Id: I8421b126d680f69141a361c1e77223fe2bf4a325
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|
2e5a68c319aaa0a19313c2f7689f2665fe74e264 |
|
24-Feb-2017 |
Daniel Nishi <dhnishi@google.com> |
Add the new package stats query to wrapper. Bug: 35754646 Test: Settings unit test Change-Id: I4b3cb93817ab998e9508c49c1aced66f6378806c
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|
3965e0207cef1200834911c4ab61c992e7c478a6 |
|
02-Feb-2017 |
Salvador Martinez <dehboxturtle@google.com> |
moved shared classes from settings to settingslib These classes are needed in StorageManager but are used by settings so I moved them into settingsLib. Test: ?? Investigating Bug: 34768442 Change-Id: I59c2f6c714d8e282d4781899127c22f8537e81af
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/applications/StorageStatsSource.java
|