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
KeyChainService.setGrant() now throws an IllegalArguementException if
the alias passed to it does not have an exisitng key. So
DPMS.setKeyGrantForApp() and DMPS.setKeyGrantToWifiAuth() will also now
throw IllegalArgumentExceptions in the senario described above. As this
will propagaet up to the DPM API's that call these functions, we will
have to gate this new behavios on DPC's target SDK level.
So if DPC targets DPC U+ : throw exception
else : return false
Fixes: 175101461
Test: n/a
Topic: make-GrantKeyPairToApp-And-grantKeyPairToWifiAuth-Throw-Exception
Change-Id: I995227b633e2fd60dad096e35f92cb539a9389d4
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
This provides a sandbox-like scaled environment on client side.
- This prevents the metrics and config from being scaled multiple
times because the entry points are only called from server side,
there won't have reentrancy for applying the scale.
- App's configuration callback method can get scaled config.
- If override scale is enabled, the legacy compat mode will be
skipped. That avoids mixing different approaches of scaling.
- Legacy compat mode is to simulate a 320dp x 480dp screen
size with density 160 (the surface scale and config scale
are different).
- Override scale is to downscale the app for better performance
(the surface scale and config scale are the same).
Bug: 238416387
Bug: 240335717
Test: atest ActivityThreadTest#testOverrideScale
Test: atest CtsWindowManagerDeviceTestCases:CompatScaleTests
Test: am compat enable DOWNSCALED $pkg
am compat enable DOWNSCALE_50 $pkg
Change-Id: I0ddf333996f229063511273f8aeb3867c9ba8bda
Before, we store the TaskFragmentToken in ActivityClientRecord from
LaunchActivityItem, which won't update if the Activity is relaunched.
Now, we update the token when the activity is reparented to make sure
the token is up-to-date when relaunched.
Also make sure that when activity is destroyed, it is no longer
available using SplitController#getContainerWithActivity(Activity).
Bug: 243330085
Test: atest WMJetpackUnitTests:TaskFragmentContainerTest
Change-Id: I37f1a442c6f1bfb40f04f61eb4f9a3d8d09733ee
This change
- adds a new private API in dream manager that allows a client with
write dream permission to set a system dream component, which takes
precedence over user configured dream
- fixes startDream() API in DreamManager which shouldn't take in a
component name
Test: atest SystemDreamTest
Bug: 222529147
Change-Id: Iee9a0af1071e5ed57fa5bd4b0d06d8178118116e
Test: unit test and cts test
Ignore-AOSP-First: confidential feature
BUG: 242480433
Change-Id: I0fd2950eea267d56fbd8e89ecc52fdd590992e75
Merged-In: I0fd2950eea267d56fbd8e89ecc52fdd590992e75
(cherry picked from commit 44eafb8f58)
