Test: Manual:
1. Create a work profile via TestDPC (go/testdpc)
2. Set a work profile lock pattern/PIN/password via Settings > Security
3. Launch the work profile instance of TestDPC
4. Scroll down to "Lock screen"
5. Tap "Lock screen restrictions"
6. Select the "Work profile" tab
7. Set "Max password failures for local wipe" to 3
8. Lock & unlock the screen
9. Launch work profile app
10. Enter the wrong pattern/PIN/password >3 times
Before: Work profile is not deleted
After: Work profile is deleted and appropriate dialog is shown
Fixes: 148374841
Change-Id: I45a0aa7ac83f67603c6cf0a06337f8a34c38586f
- Adds some user education strings that aren't used yet, that'll
be fixed in a follow up
- Removes some strings that aren't ever used
Test: treehugger
Bug: 151965589
Change-Id: I31a4dcb518b37505ed07fc2d454ddfec7598fb01
Deflake NotificationEntryManagerInflationTest by moving back
to the countdown latch approach and providing our own executor
to AsyncInflationTask.
It was infeasible to depend on the exact number of main thread messages
as other main thread messages from other tests could interfere. Thus.
we move back to the countdown latch for when NotificationEntryManager
finishes inflation. This makes us dependent on the listener API for
determining when inflation is finished, but it's unlikely we can do
better unless we can inject an executor into RowInflaterTask.
In addition, using AsyncTask's SERIAL_EXECUTOR on hwasan builds seemed
to be much slower than normal. This lead to other tests' AysncTask
work delaying the work in this test and leading to the timeout
happening before inflation finished. By providing a test executor
instead and synchronously controlling its execution, we avoid this
issue.
Bug: 150618180
Test: atest --iterations 100 NotificationEntryManagerInflationTest
Test: atest SystemUITests
Test: A forrest run coming soon!
Change-Id: I87c6e2d216c8f26aaf340d311f618c9dccaba8af
An accidental ID collision in volume dialog logging had
RINGER_MODE_NORMAL and ZEN_MODE_OFF both on ID 156. Move both to new
IDs (334, 335).
Fixes: 151632114
Test: atest SystemUITests
Change-Id: Ic24fd3ac30721c93eae9f0b164c8a2a7d3aee118
This CL adds a way to track BroadcastReceivers that are leaking in test
cases that use SysuiTestCase (all of SystemUITests). Every receiver that
is registered with Context is recorded and those that are not
unregistered are logged as a Warning. After each test, receivers are
unregistered so they don't polute following tests.
Additionally, if a BroadcastDispatcher is instantiated, a Fake is
provided that will also track leaked receivers and log them as Info (as
BroadcastDispatcher will only keep WeakReferences).
This is a separate tracker done directly in SysuiTestableContext instead
of using LeakCheckedTest or a LeakChecker as that is usually pretty
stringent (it will fail the test).
Test: SystemUITests
Bug: 151614195
Change-Id: I11afb49ce3bbc51d98fa069ba4074c852d07bcce
startTethering with type is deprecated way and may not be exposed in
TetheringManager. The usage should be replaced by startTethering with
TetheringRequest.
Bug: 151918384
Test: m, atest
Change-Id: I9c26db3639857a8909be1888046fc942b8a51182
This allows other parties to directly interact with PipTaskOrganizer.
Bug: 147361175
Test: None yet
Change-Id: I0047f1cad5f55ddc4bd35ed892bb10ad4ded0fe2
It is less than ideal to see subtitles popping in. Persist and restore them.
Bug: 150876640
Test: atest ControlsControllerImplTest AllModelTest ControlsBindingControllerImplTest ControlsFavoritePersistenceWrapperTest
Change-Id: I449ac020ccdd03f8c42b0a29eef21764514470a0
This adds the ability to show/hide menu based on hover enter/exit
events.
This also changes the InputConsumer so that it's now attached to the
pinned RootTask (Stack)'s SurfaceControl, so that the PipMenuActivity
appearing will not cause a new HOVER_EXIT + HOVER_ENTER pair event.
Bug: 144184591
Test: atest PipTests
Hover in/out of PIP activity, see menu show/hide.
Change-Id: I79536eb52cd234a82cbb7cb3004e31ada3ca0433
Test: Manual:
1. Enter "BiometricPrompt Demo" app.
2. Check "Allow device credential", uncheck "Require confirmation".
3. Check any Radio button. (e.g. Persist across configuration changes)
4. Rotate DUT to landscape mode.
5. Tap the "AUTHENTICATE" then deliberately unrecognized.
6. Tap "Use pattern" button.
Before: The pattern entry UI is clipped and the text is not visible.
After: The pattern entry UI fits on the screen and is interactable.
Fixes: 149545148
Change-Id: Iefc0a7ce60a8caeb537b46ec821df0ea4d80e843
When no controls have been loaded, and a preferred package has been
set, bind to the preferred service and ask it for suggested controls
to seed the stored favorites.
Bug: 151817620
Test: atest StatefulControlSubscriberTest ControlsBindingControllerImplTest ControlsControllerImplTest ControlsProviderLifecycleManagerTest ServiceWrapperTest
Change-Id: I1e51b8998b8379f08c2b995b7cbe23d1037bd840
CameraManager.AvailabilityCallback will notifyCameraInactive()
at initial stage, and cause NPE when mCutoutViews is NULL
Initialize mCutoutView at early stage
Bug: 151706640
Test: manual boot device
Test atest SystemUITests
Change-Id: I2008342d15bb589f85bb99fcc35ede96ef9678bd
