Toasts are used by framework/supportlib code, so don't block them
outright.
Bug: 36539171
Test: manual
Change-Id: Ic5e1c599021224c3727cb18554ea04e6833fef2a
Added deletePreloadsFileCache that can be called from settings app.
Modified freeStorageAndNotify to call deletePreloadsFileCache if the
cache has expired, or aggressive flag is set.
Bug: 34690396
Test: Manual
Change-Id: Ia097cd2f62ad501644be1c2cc573c249d8cfbf55
Change-Id: I58e81f5f473ac1cffb8947cd713bb1249ce00305
Fixes: 33072933
Test: add/remove/update the instant app installer and see that it changes dynamically
ActivityManagerService will send the details to dumpstate and
BugreportProgressService will get the details from dumpstate and use
that for the notification.
Bug: 33561517
Test: Modify TelephonyMonitor to use this API and ensure that the
notification uses that the title and description sent as arguments
to the API. File a bug using betterBug and ensure that the
information gets populated automatically.
Change-Id: I455f1df2278e5d569dd19c74245a0704dcf5a321
Breaks work profile creation among other multi user issues
Bug: 36530935
This reverts commit 85942c2bc69385eb326cfe0e15ad9223bf1cffb5.
Change-Id: I0b5901a02ca590b7e8121aa8babe5b1c5819eca7
Using the word "atomic" has too much baggage relating to locking
guarantees, so move to something softer.
Add isQuotaSupported() for CTS tests.
Move CacheQuotaStrategy over to using SparseLongArray, which has a
more efficient memory footprint inside the system server.
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest
Bug: 35812899, 35684969, 36482620
Change-Id: I894f53e6f3bc76c77d1bb18c51db14833df14a49
This limits excessive logs from MediaRouter and MediaSessionRecord
- MediaRouter: Leave log only if there's change in the audio route.
- MediaSessionRecord: Leave log for the controller callback instead of
dumping verbose stack traces.
Bug: 36497125
Test: Manual test
Change-Id: Ie0fe9f33388d1aa9f25c26b3b3f7c71fec409ba8
It seems the new fingerprint daemon doesn't recover as quickly as before
and there's a finite chance reconnecting immediately will fail.
This changes the framework to be more robust about recovering by:
1. explicitly connecting to the daemon in isHardwareDetected()
2. ensuring we remove the current client when daemon death is detected
3. reset the daemon whenever we get HW_UNAVAILABLE so we try again
Test: manually kill daemon and verify FingerprintService reconnects
Partial fix for bug 36181191
Change-Id: Id530ed62be58b33af5b5b60083f3a69e4e8cd8bf
Bonehead mistake; we were applying the post-resolution filters twice.
Don't do that!
Test: build and see that the installer runs when trying to launch a split that's not on the device
Change-Id: Ice65cdd7cc85d0394422009ba42f388f0ec2595c
Instant Apps wont be started by these broadcasts, but if they're running
it gives them a chance to be good citizens on the device and help out
with a space crunch.
Test: manual
Bug: 33350280
Change-Id: I1700153b1c698a29e1e35535f64062544d071cab
AccountManager needs to pass the app's uid explicitly in order for the
channel lookup to not fail. Requires separate API that only system can
call.
Bug: 36511867
Test: Install Clankium and reboot device, observe Notification
Change-Id: I6ddd87d755b4b2129565dd275e799b0349a80936
