- Revert 942a85c6d6
- Use a more specific fix for the triggering of PiP from the SysUI
screenshot share intent.
Bug: 63984385
Bug: 63581685
Test: android.server.cts.ActivityManagerPinnedStackTests
Test: Click share on the screenshot action, ensure activity below does
not enter PiP
Change-Id: Id8041d50dd429030c20940dca19e5c62bbc0c6a4
This CL fixes following issues:
1. The text on the button currently is black (should be white).
2. Clicking on it turns the screen off but doesn't disable the enabled
profile.
Bug: 64227431
Test: E2E
Change-Id: I87eaeb348c32af610a375912ae0aa5c7aa25dba7
The data usage dialog is displayed every time rotating the device.
To solve this issue, prevent NetworkOverLimitActivity from being
re-created when rotating the device.
Bug: 36801016
Test: manual - show NetworkOverLimitActivity and rotate the device
Change-Id: I51429aa49157756107e9b3fa9d450f82f894dcab
Turning overlays on and off takes time,
it also doesn't allow us to have fine control
over which view is using which theme.
Lock screen colors are now driven by themes.
Change-Id: Ie8860d00dbb0705ed76edf60a9d3030618dd21ca
Fixes: 63751714
Test: Visual. Set wallpapers, unlock.
Test: runtest -x packages/SystemUI/tests/src/com/android/keyguard/KeyguardSecurityContainerTest.java
Test: runtest -x tests/Internal/src/com/android/internal/colorextraction/ColorExtractorTest.java
Test: systrace
Turning overlays on and off takes time,
it also doesn't allow us to have fine control
over which view is using which theme.
Lock screen colors are now driven by themes.
Change-Id: I4b5db6234cafebbe8eaa952781c038370a11488b
Fixes: 63751714
Test: Visual. Set wallpapers, unlock.
Test: runtest -x tests/Internal/src/com/android/internal/colorextraction/ColorExtractorTest.java
Test: systrace
This also cleans up unused PIP activities from the Manifest file.
Bug: 37912313
Test: Manual test as follows
- Checked that my test app crashes when it sends intent to start
the PIP menu.
- Checked that starting the PIP menu activity with the am command
doesn't cause System UI to be crash.
Change-Id: I3a8171fcf6017c2616b8e83ab8a281b5d7e56ab7
Hardware acceleration is enabled on the application level in the
manifest. This cleanup-only CL removes redundant calls to enable
hardware acceleration on the level of activity, window, or view.
Test: Ran systemUI jank tests checking for lack of jankiness.
Change-Id: I37a9b687be3aaf95f9ba497e99cabd5f8c73ace1
Added new theme Theme.DeviceDefault.QuickSettings.Dialog and applied it
to the brightness dialog.
Fixes: 62010126
Test: visual
Change-Id: I3bc1116a227d5e62d8624c9a4911771152f3ced0
This is one of many CLs to go through the PackageManager API surface
and filter access depending upon the requested information and the caller.
In this change, we filter ActivityInfo, ApplicationInfo and PackageInfo.
Bug: 35871369
Test: bit FrameworksCoreTests:android.content.pm.PackageManagerTests
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.EphemeralTest
Change-Id: Iaefd73f912ab1c7e1844e72625388455f783a362
Add the NETWORK_SETTINGS permission to the sysui components so we can
properly check for allowed callers in WifiService.
Bug: 36760523
Test: make
Change-Id: Ia054ffad7a9508e0d80f7b3a444691373ad1924f
...hide themselves
The activity manager now keeps track of all apps that are running
foreground services and builds a notification showing them to the
user. We ensure they are shown to the user for at least 30 seconds
(configurable). If foreground services are executed while the
screen is off, their apps will be shown to the user for at least
30 seconds after the screen turns back on.
While doing this I am also adding a new process state to distinguish
between "important background" stuff that should bypass bg check vs.
ones that don't. By default, these now no longer bypass bg check,
which is really the expected (and documented) behavior. There is a
new bind flag to allow them to bypass bg check, which is currently
only used by the IME.
Also add some new job scheduler commands that will be used to
write new tests cases for jobs timing out.
Bug: 36891897
Test: manual
Change-Id: Ied3f7b56444254513fd776f06b88bc0e54704958
In an always-on display environment the device may go into doze, but
SysUI will still need to update the display on an ongoing basis.
Bug 36506772
Test: manual
Change-Id: I0b20ba7c352bac7c278f659f0e29496cc342d381
Adding new permission for changing accessibility volume
to allow system UI to change it. Also providing audio
manager with a whitelist of bound accessibility service
uids so it can allow servics to change the volume.
Bug: 36569297
Test: Adding CTS test in linked CL.
Change-Id: I4f327e3a251fc3780c5957f41217c2ef5bb8b16e
b/35307747 moved these intents from android. to com.android. Change
filters in AndroidManifest so that the new intents are not filtered out
and actually get delivered.
Bug: 36085764
Change-Id: I7120f28e56d71b6bfa19dd59624d992ded79501c
Fixes: 36085764
Test: none
Make modifying the STREAM_ACCESSIBILITY volume conditional
to have the BIND_ACCESSIBILITY_SERVICE permission.
Add BIND_ACCESSIBILITY_SERVICE permission to sysUI.
Test: cts-tradefed run cts -m CtsMediaTestCases -t android.media.cts.AudioManagerTest#testAccessibilityVolume
Bug: 34379420
Bug: 30448020
Change-Id: I9f26affccd953bd8473d06822857edf92fef4ba8
Exposing actions from the PIP InputConsumer to accessibility,
stripping all actions from a covered PIP app, and adding the
InputConsumer's actions on the PIP app's root view.
We were also using an "undefined" accessibility ID to mean
three different things: a root view, a host view of a virtual
view hierarchy, and a truly undefined view. I've introduced
new values for cases where the id could be defined.
Also gathering all window IDs into one place to reduce the
chance of collisions.
Bug: 34773134
Test: In progress. Current cts passes.
Change-Id: I97269741a292cf406272bf02359c76c396f84640
This patch will remove the Recents TV Code from SystemUI.
Test: To test this removes the Recents Feature and has no
side effects, try to launch recents with long-press HOME. This
should result in launching the phone version of recents.
BUG: 36035359
Change-Id: I9026b480968575ce08e1ce344512f168fdc5fe87
Adds a service for monitoring the amount of tracked garbage.
If it exceeds reasonable levels, a notification with a leak
report is posted.
Test: runtest systemui
Change-Id: Ib55281f2aac557743b97c46bc616688261c72e9c
SINGLE_TOP is only guaranteed to work within the current task stack.
If multiple stacks are inactive in the background (eg. temporarily
switching from freeform mode to fullscreen mode by maximising one
activity) some tasks might get missed out and stay visible.
Test: manual -- start two work activities, one in fullscreen & one in freeform. start a personal
Test: activity in freeform too. switch to the fullscreen work app and lock the profile using
Test: `adb shell service call trust 6 i32 $USER_ID i32 1`
Test: __outcome after change__
Test: a) locking work profile should bring up the work password prompt in fullscreen
Test: b) skipping the prompt and switching to the personal freeform app should keep the freeform
Test: work app hidden by WorkLockActivity
Test: __outcome before change__
Test: Only (a) happened, for step (b) the work app was still visible
Bug: 31001762
Change-Id: I5979c5b12670a21c7bcd59e222fc518d395e3e29
No longer need to look up the application info, target SDK is
explicitly passed in to the check. For the external method, we
change this to just checked to see if background is completely
disabled, which doesn't need a target SDK check (and is the only
thing any of the current clients care about).
Now allow SystemUI to put targets of notification pending intents
on the temporary whitelist when they fire, so developers can avoid
dealing with background restrictions in this case (if the user
interacts with their notification, they will temporarily be
considered in the foreground).
Remove any thoughts of enforing restrictions on registerReceiver(),
so we don't need to deal with target SDK versions there (which can't
be done all that efficiently).
Also bring back the old "allow starts coming from foreground apps"
only for the MODE_IGNORE app op, since it should provide some
better compatibility.
Test: ran them.
Change-Id: Id4ea7f992d12ce4bd8e54f1dbaeb4a460a3dee59
