For example if user 0 has no lock screen set, but the work user does,
and the "hide all notifications while locked" field is set, we should
hide those notifications because they are supposed to be hidden behind
the work lock screen.
Fix: 32585026
Test: statusbartest/NotificationTestList.java
Change-Id: I29243f683fd4ef2d5fc71a40cd1e37ee29c5679c
(snooze indeterminately and unsnooze)
Test: runtest systemui-notification and cts tests in same topic.
Change-Id: I5ce74638f55ed796bc6b26af167b32b0040f4222
The integrity checking features never shipped as part of a release.
Delete the stale code.
This conceptually reverts the following commits:
* c7d64c134a
* ee2b492832
Test: Device boots and no obvious problems.
Change-Id: I8d1589b38ddbcdf26f5132476b8cdfba7ef439cd
Add a new activity intent action which will be launched after
provisioning has successfully completed.
Currently when provisioning is done we junt send an ordered broadcast
for PO and a normal brodcast for DO case. This results in HOME screen
being launched for 2 sec. To remove this jank we have introduced a
new intent action which can be directly received by the DPC in their
post provisioning activity.
Test: b/33138551, this bug tracks the cts coverage for the new action.
Bug: 30956199
Change-Id: I889b0cec74799bb7be93de48d46d5da68f17be92
The getLastSecurityLogRetrievalTime(), getLastBugReportRequestTime()
and getLastNetworkLogRetrievalTime() methods are meant to be used by
system code. However, there is no harm in allowing the DO to access the
information they return - because it is information about actions that
the DO itself took.
The advantage of opening up these methods to the DO is that we can
CTS-test them.
Bug: 32692748
Test: DevicePolicyManager unit test + CTS test in separate CL
Change-Id: I1470fca2a82b9955f7aed5e8b50220bea8b56fc9
When a test fails in layoutlib, store the resulting png files in
out/failures subdirectory of the current working directory.
That avoids the risk of collisions if tests for several branches
of layoutlib are run at the same time.
Test: Run tests in layoutlib with at least one failing test
Change-Id: I31594a871e481e6aa410a165926ce544dc7ddcf2
(cherry picked from commit 82ebb9058479de56860f348ab969160e0d8294b6)
Shadows could be painted outside of the allowed drawing region
for the components for which they are the shadow.
Bug: http://b.android.com/215402
Change-Id: I2d2821b745147f3723e8f11d648094fcd684fe51
(cherry picked from commit 9702fffc768db43d0aba4fb1bea54af50af11361)
assertPackageIsValid was checking policyFlags (which are PackageParser
parseFlags) for flags defined in the SCAN_* values. This was always
subtly and non-visibly broken, but turned into a full scale breakage
when change 5b29ecad48 was merged, and
one of the flags that *happened* to have the same value in the PARSE_
and SCAN_ flagset changed.
Test: make, boot, update system app, update playstore app.
Bug: 33124572
Bug: 33126202
Change-Id: I482f420b2a9c8af38b17d174f1a2ec36c762f58e
This class was added in ServiceManager.java in commit 49ca529a85.
Layoutlib rewrites the entire ServiceManager class, so it also
needs to define ServiceNotFoundException.
Test: TestDelegates.testMethodDelegates
Change-Id: Ia68399e8baa973ae961eabe929ca3d1019f20ba7
Add getBindDeviceAdminTargetUsers API. To be used
for the device or profile owner in a COMP setup to
know the UserHandle of their instance running on
the other profile.
Bug: 31952368,33033966
Test: cts-tradefed run cts --module DevicePolicyManager --test com.android.cts.devicepolicy.DeviceOwnerPlusManagedProfileTest
Change-Id: I05c9ac0f6c3cdce1ec17cf2910ca7a7214064af2
