Bug: 241763149
Refactor the sCorkLock into sCorkLock, which protects code that
specifically supports corking, and sGlobalLock, which protects all
other code that touches global objects (like the list of all caches).
Deadlock was not actually observed in the bug and has never been
reported, but the possibility was identified and is being fixed here.
Bypass the bulk of disableLocal(name) if the name has already been
bypassed. This speeds repeated calls to disableLocal() by not
iterating over sCaches.
Many threads were terminated by a watchdog while iterating over
sCaches inside disableLocal(). It is not known why this block of code
was running so often when the time out expired.
An open question is whether or not disabled caches should be removed
from the sCaches array. The only reason to leave them in the array is
to report on them during dumpsys, but this seems like a small benefit
Test: atest
* FrameworksCoreTests:IpcDataCacheTest
* FrameworksCoreTests:PropertyInvalidatedCacheTests
* CtsOsTestCases:IpcDataCacheTest
Change-Id: I4c298f380044c0be93cdb47d66d7d7e2b260004f
This allows us to manually specify which app op should have noteOp
events collected for them, if applicable
Bug: 44518166
Test: manual
Change-Id: I3988679fd9b8ccedde37a47cacc0ac2c276b78e6
Revert submission 19776394-safer-implicit-intents
Reason for revert: DroidMonitor: Potential culprit for Bug b/246818637 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted Changes:
I66227a4fa:Update PackageManager test in Car to adapt to safe...
I779f3d6ee:CTS tests for safer implicit intents
I41c48a412:Verify that the component is exported
Change-Id: I8484d317afc9a1d845b3394828062615b5fd2066
Previously, binder txns were only traced for txns from sysui/launcher
to system_server.
ag/Iffc4bb534d239c07d2e4d43ab43a9ed76abe7496 enabled binder txn tracking
more broadly
Removed the special case for sysui/launcher and cleaned up the code
Test: Manual
Bug: 161393989
Change-Id: I9d46d2362ca0ca33bc2477d68092f7ba5fe9c8ac
Reflect the QUERY_ADMIN_POLICY permission check instead of System app
check in the Java doc.
Bug: 239984134
Test: N/A - just documentation change
Change-Id: I49d6b757214fde216da5b7ac7624107e3488ef77
Add a list of app ops that are not tied to a permission, but should have
note events sent to users. Also add RECEIVE_AMBIENT_TRIGGER_AUDIO to
systemApi
Fixes: 44518166
Test: manual
Change-Id: Iff9d3f5a75bee0a65be6cbb0eaa5151d81f8902a
As ownerName has been removed from OwnersData.ownerInfo, there is no need to take
it as an argument in DPMS.setDeviceOwener or for any other methods that
call it.
Bug: 240562946
Test: atest FrameworksServicesTests:com.android.server.devicepolicy.DevicePolicyManagerTest
Test: atest SetDeviceownerPolicyTaskTest
Change-Id: I7748a5cf152e9327854623fbac5f8ed3f5d3f28a
As ownerName is no longer a parameter of OwnersData.ownerInfo, it can
be removed as a argument from setProfileOwner().
Bug: 240562946
Test: atest FrameworksServicesTests:com.android.server.devicepolicy.DevicePolicyManagerTest
Change-Id: Ie996174f442db3406b6d5122d17ce127f4d6554c
Converge towards always using IApplicationThread to identify the
remote caller that is finishing a broadcast. This pivot will enable
us to scale nicely to our future redesigned per-app stack, since that
will still only ever dispatch a single broadcast per app.
Add explicit setCurrent() and clearCurrent() methods to ensure that
all BroadcastRecord fields are updated consistently.
Bug: 243656033
Test: atest CtsContentTestCases:BroadcastReceiverTest
Test: atest FrameworksMockingServicesTests:BroadcastQueueTest
Change-Id: I3db8382798bb25fabe20aa9864cf6f8831b64371
So we have a complete picture about all packages loaded into a process.
This will be used to check if installing a package causes a process to
be killed.
Note if pkgList or pkgDeps contain the package to be installed, the process
will be killed during install.
Bug: 235306967
Test: m
Change-Id: I052185f8d54717e65fa1fddaa42ca80ebbf15a5d
disableflags package was created by ag/19795082.
Bug: 240590557
Test: atest SystemUITests
Test: manual: Verify we still get disable state logs
Change-Id: Ia02ba83e653197e4c77deb5cd7db1e805914e340
This change both prevents any rules from being unable to be written to disk and also avoids risk of running out of memory while handling all the zen rules.
Bug: 242703460
Bug: 242703505
Bug: 242703780
Bug: 242704043
Bug: 243794204
Test: cts AutomaticZenRuleTest; atest android.app.AutomaticZenRuleTest; manually confirmed each exploit example either saves the rule successfully with a truncated string (in the case of name & conditionId) or may fail to save the rule at all (if the owner/configactivity is invalid). Additionally ran the memory-exhausting PoC without device crashes.
Change-Id: I110172a43f28528dd274b3b346eb29c3796ff2c6
Merged-In: I110172a43f28528dd274b3b346eb29c3796ff2c6
(cherry picked from commit de172ba0d4)
