am: f8a5719cfc -s ours
am skip reason: change_id Iff36d5a10e6c8ee8978a5842af8f19efc10c0a91 with SHA1 5579604a1d is in history
Change-Id: Iceeedbce2cc16fb2c46b944d80a3c5363ea40de7
If we are acquiring a content provider, but the hosting process
is dying, wait for its death notification come in, before
restart this process.
Bug: 141857656
Test: manual
Change-Id: Ib2a8014bb3f22485172d0574cfce14bc6895034b
Problem introduced during code refactor.
Fixes: 145015624
Test: Camera launchs from home activity.
Change-Id: I9ed474471ccbcc333892301b06e79a58cef5a207
UsageStatsDatabase#init was being called twice every time - once when
the usage stats service was initialized and once when the user was
unlocked. However, this was unnecessary and doing duplicate work since
on user unlock, when the service is initialized, the database is also
initialized.
Bug: n/a
Test: atest UsageStatsTest
Change-Id: Ic74ba3ff8a0b68c97340ffe25b19065e1a046731
This commit makes the the API WifiScanner.setScanningEnabled() a System
API to allow priviliged apps to use it.
Bug: 140541571
Test: atest com.android.wifi.server
Change-Id: Id7377415699f2d8a8aea396889716dca1e23ecd5
Prior to this change, we were resolving the mime type of a given intent
while holding the package lock. With this change, we instead rely on the
preferred-activity declaration to define the mime type if it's
important, removing need for an activity manager service call and the
potential for deadlock.
Bug: 143105100
Test: Manual; sideload to /system/etc/preferred-apps/ and reset app preferences
Change-Id: Ie0b124216b49a1147bd5c2e82cf8c7cadb3f08ac
This is the first step in extracting the power whitelist from
DeviceIdleController. The whitelist will stay inside the JobScheduler
mainline module boundary, so all calls will have to be made through a
stable API. Eventually, all users of IDeviceIdleController will be
migrated to this interface.
Bug: 140141678
Bug: 141155196
Bug: 144864180
Test: atest PowerWhitelistTest
Change-Id: I8468e74ac8fe6611bfa957d4f5093c8d15be1299
ag/9507174 moved the profile badging logic, but accidently also touched
the non-profile badging logic. This cl just reverts that line back to
how it was originally.
Note that, in DevicePolicyManager terminology, the managed user is
called a 'profile', but in UserManager terminology, it is not. In this
commit message, I am using the word 'profile' in the UserManager sense.
Test: Manually confirmed with TestDPC that a managed non-profile user
has a badge
Fixes: 144831236
Change-Id: Icd4f215d49f317a0df8065d3c48c68eee0fd5b2c
Adds reporting per-display configuration changes to
hierarchy listeners. On system-ui's side, the
DisplayWindowController then dispatches to other registrants
within the process.
Bug: 133381284
Test: Added testDisplayWindowListener
Change-Id: I68c4e9e229b97a9e91ad0d4f5276447a947c413b
There's no need for the black frame to call setLayerStack since it's a
child of the overlay layer. Calling setLayerStack does nothing, but it
will produce an error message in SurfaceFlinger since the caller is
trying to set a specified layerStack on a layer that's not the root.
Deleting thihs code to remove the error spam in logcat.
Also removed it from the Watermark code since it's also a child of the
overlay layer.
Bug: 144824244
Test: No more error log about invalid layerStack in SF
Change-Id: I2f64d50d81af9caf8debe289c4a8eda7c2a61031
