Fixing a typo in the previous commit: s/remove/put/
Bug: 153013604
Test: ran CTS tests on sdk_gphone_x86
Change-Id: Iabe8ce51f38ac921aa5cc0e78b559e4a512b9273
This removes the dependency on re-delivery of sticky broadcasts by
having a single point in the system that listens to
RINGER_MODE_CHANGED_ACTION and RINGER_MODE_INTERNAL_CHANGED_ACTION.
Also, added some global mocks for Notification tests that were
constructing KeyguardUpdateMonitor (after many injections).
Also, added mock in KeyguardSecurityContainerTest.
Test: manual
Test: atest SystemUITests
Bug: 151641451
Change-Id: Ie81109cf1fe077bc4790f7a4e501df69dbb2323b
In quick switch flows, launcher will first swipe task snapshot
through recents animation, and then start new task with custom animation
options through startActivityFromRecents after gesture finish detected,
and then finish recents animation finally.
But that way user may experience flickering before the new task launch
and recents animation finish.
To improve quick switch flickering, we ignore the new task's custom
animation from recents and generate task remote animation target,
and then trigger a callback for launcher to control/animate this
task surface, more like a part of RecentsAnimation,
Also, adding removeTask method for launcher can flexibility remove the
new task animation target once no need to animate, so that launcher
can decide when to finish recents animation.
Bug: 152480470
Test: manual as below steps:
1) Doing quick switch task.
2) Make sure launcher can receive onTaskAppeared callback.
3) Make sure launcher calls removeTask successfully.
4) Make sure launcher can finish recents animation after 3).
Change-Id: I0692a280a49719229fa8871509bad37a1343a00f
There is no need for a content description on the associated icon, as
the title is sufficient.
Bug: 153288023
Bug: 153291530
Test: talkback
Change-Id: I8617151cbbbb24f437e93a7c106997ef355206b6
Request the IME to hide current inline suggestion on committing.
Bug: 149945531
Test: atest InlineLoginActivityTest
Test: atest InlineAugmentedLoginActivityTest
Change-Id: Ia19aebb7d84c6d858fa93ee51df1bbbf7d92eafe
Because of internal implementation of one way binder calls, in order to
unblock the boot phase, we need to put both the binder call and the
filedescriptor in the background thread.
Original boot time: 17758.6ms
New boot time: 17608.0ms
Bug: 130773130
Test: DeviceBootTest.DeviceBootTest#SuccessiveBootTest
Change-Id: Ib3524418a387c5902af8139e1b2aee82525b8e04
These stubs contain the libcore sources inside them, so need not
compile against core_current.
Also rename the defaults rule to be in line with the new neverallow.
Bug: 144149403
Test: m
Change-Id: I5f1b01875b0073f942c692882db157a8c5788ce0
Merged-In: I5f1b01875b0073f942c692882db157a8c5788ce0
Looks like this is caused by calling removeView right before addView, which happens when we recreate the dismiss target. Sometimes, removeView has not completed by the time we addView again.
I wasn't able to reproduce the crash, but other places in sysui use removeViewImmediate for this purpose.
Bug: 153551432
Test: try rotating the screen a bunch with a PIP visible
Change-Id: Ic96173c1273b8476280a7daf63340bbe9613b21e
This patch uses Instrumentation parameter inside
getDefaultLauncher function to obtain user ID
from it and get default launcher namely for that
user as setDefaultLauncher function sets launcher
for the user from Instrumentation context. This
fixes incorrect launcher settings for the cases
that use two sequential calls to get/set
default launcher.
Bug: 145774461
Test: run cts -m CtsShortcutHostTestCases -t \
android.content.pm.cts.shortcuthost.ShortcutManagerMultiuserTest#testSecondaryUser
Signed-off-by: Sergii Iegorov <sergii.iegorov@globallogic.com>
Change-Id: I8941f5648ad783c7681fdb56677e855756db957d
Merged-in: I8941f5648ad783c7681fdb56677e855756db957d
* accountTypesWithManagementDisabled
* disableScreenCapture
For security logging nothing has to be done since the state is
stored in a system property, just changed it so that the logging
will be started after the migration and only events for the
right user are logged.
Also removed the todo about hardening for power cut case, the
risk of additional complexity sees to outweight the benefit.
Bug: 149075700
Test: atest DevicePolicyManagerServiceMigrationTest
Change-Id: I3a58325f2d6f415e51998c5096c5fc123d26602d
Enable for testing controls seeding. Make sure subscriptions are
cleaned up properly. Up the seeding limit to 6. If we received our
requested control limit on load, cancel() the subscription and
immediately load.
Bug: 153455870
Test: manual, use 'Reset' button to test seeding process
Change-Id: I536315de423c49231e77c0b1b24ad20883ddaae7
Also, do not bind mount storage obb and data dirs if mount external is
in pass_through mode.
Fix: 151219235
Fix: 152395018
Fix: 152490627
Test: atest AdoptableHostTest
Change-Id: I77a86be5582ded0915b0a8a49d2b2a8c17fe58b7
This method consolidates logic of testing whenever rebooting userspace
is supported in a place that can be used both from
PowerMager.isRebootingUserspaceSupported() API and from
PowerManagerService.reboot() implementation.
Consequently, this makes `adb shell svc power reboot userspace` also
benefit from that check, and fail userspace reboot on devices that don't
support it.
Also tweaked logic of ignoring RemoteException to take into account
userspace reboot.
Test: adb root
Test: adb shell setprop init.userspace_reboot.is_supported 0
Test: adb shell svc power reboot userspace & verified error message
Test: adb shell setprop init.userspace_reboot.is_supported 1
Test: adb shell svc power reboot userspace & verified no error message
Test: atest PowerManagerTest
Test: atest CtsUserspaceRebootHostSideTestCases
Bug: 152803929
Change-Id: I2d3a8e0ae1320c408a838c5c5fdf4cd977b167b3
* Modified setAutoTimeRequired to call
pushUserRestrictions after requireAutoTime
in the active admin is set.
* Modified addSyntheticRestrictions in the
active admin to include the auto time
required case.
Bug: 145604635
Test: atest com.android.server.devicepolicy.DevicePolicyManagerTest
atest com.android.server.devicepolicy.DevicePolicyManagerServiceMigrationTest
Change-Id: Ida4952eeec8ec12573c4049a9bf8e0ce6a951a86
The config overrides were only computed for leaf tasks. So, the
config of the organized tasks were inherited from the display,
which was still fullscreen size. This was not right especially
for split-screen organizer tasks because the configuration could
be used by the organizers.
Also remove requesting override windowing mode as fullscreen for
home tasks, the config was updated to fullscreen or
split-screen-secondary while resolving override config instead.
Bug: 152408408
Test: Enter split-screen and show IME
Change-Id: Ie6737cb5e9655c57724fc140c6b6fde3a96be6ab
If it is frozen, interface has to implement getInterface(Version|Hash)
Bug: 153501202
Test: m FrameworksServicesTests
Change-Id: Ia9423a7fe524ff225435344b527728ec2646adfc
Merged-In: Ia9423a7fe524ff225435344b527728ec2646adfc
