When the Activity Manager informs the Window Manager that a stack has
been removed, it can opt to hold onto the stack (such as when an
animation is in progress). This can lead to inconsistencies where the
Window Manager can report a stack back to the Activity Manager that
has since been removed.
This changelist addresses one such call point in
WindowManagerService#setNewDisplayOverrideConfiguration. Deferred
removed displays are now filtered out of the returned list.
Change-Id: I5f7aad9296cec8bd56e933a71553f9cd40579378
Fixes: 71548119
Test: atest FrameworksServicesTests:com.android.server.wm.RootWindowContainerTests
There was a race condition where we notified the controlling app
already about transition start, which itself started the animation
and applied the transform of the first frame. However, a little
bit later, we applied the pending transaction from window manager,
which overrode the properties again, leading to a flicker.
Test: go/wm-smoke
Test: Press home button, observe never a flicker
Bug: Surprisingly there isn't one yet.
Change-Id: I849a1573e6fd0487b9b5c22c7a7525bc818661cc
We no longer need the notification channel for alert window
use for a process e.g. the package is uninstalled, then go ahead
and delete the channel.
Change-Id: I2dea9af0e73810f91b248ad85cab73fa4f8271f4
Fixes: 67883657
Test: steps from bug
And delete zenpaneltest - it causes other tests to fail flakily,
and isn't currently used.
Change-Id: I15a9201128656a4f75eeab6d0d250534062bfbbf
Fixes: 72785419
Test: atest SystemUITests
We should have done this every time the schema changed, and written
appropriate upgrade SQL. Unfortunately there are now devices in the
wild that initially created the database using older SQL. As such
they are missing columns. This causes them to crash when queries are
run against the DB expecting those columns to exist. As we didn't
up the version number, flashing a new build didn't cause the CREATE
SQL to run again.
Test: manual
Change-Id: I1daa263d9baa69af4abb4bebfe45586b1f9dfd0e
* changes:
MediaSession2: Rename BrowserRoot to LibraryRoot and move to updatable
MediaSession2: Move MediaSession2.CommandButton to updatable
MediaSession2: Move MediaSessionService2.MediaNotification to updatable
Pending brightness change never stored
in current brightness.
Bug: 72725570
Test: manual - non-adaptive move slider check it works, reboot check brightness was persisted.
Test: manual - adaptive - move slider check it works.
Test: manual - verify slider events are logged for adaptive and not for manual brightness
Change-Id: If2914dcb223cf4308f178c101e862e6b4ba851bb
In order to tune the API lists, we initialize the light greylist with
APIs we know are used by popular apps. All the other private APIs are
moved into dark greylist. Light greylist will be set to not warn at
all, while dark greylist will produce warnings. This will allow us to
collect logs and tune the lists without breaking all of our dogfooders.
Bug: 64382372
Bug: 72793280
Test: make
Change-Id: Ice6c487eeca8900e6a70abe1b87e8c211ef1066e