Visible apps could have sub levels within the visible category.
Scores between 101 and 199 should be attributed to visible
category instead of perceptible.
bug: 27987575
Change-Id: I2dbe8af65e6829bafc86ffb5222a5f1aeac2d8b4
This means a rotation is started while we have a transition pending,
and startFreezingDisplayLocked() called mAppTransition.freeze() to
cancel the transition by setting it to TRANSIT_UNSET but ready
immediately. Screen unfreeze will wait for mOpeningApps to empty.
handleAppTransitionReadyLocked() will remove the app from
mOpeningApps once it's drawn, and allow screen to unfreeze.
We don't add the app to mOpeningApps if the transition is neither
set nor ready. We don't have any transtition and the app won't be
removed from mOpeningApps.
bug: 27784481
bug: 27391256
Change-Id: Id2c0759732593121769c402ae0c6edde3ebc7dc6
This reverts commit ebe9c0dbebbd8c2a23a76ff827b90e66ce3813bf [1],
because it caused a regression that IME window becomes transparent on
the lock screen (Bug 28013209).
[1]: I7d406cc88aae40a8b22c1fc1d856ccb7b6bb4558
Bug: 26387930
Bug: 28013209
Change-Id: I11243703030e34b917136b69a35245e9ef73c87c
If we do not call untether, NetworkController will still think
that wlan0 is part of the LOCAL network, and thus any attempt to
use wlan0 for anything else is doomed to fail.
Bug: 27917299
Change-Id: Ibb63f6b477b85b92281d9667adf8af148deb266c
Previously, if frame extended beyond screen, override inset was set
to zero for corresponding dimension. This caused issues while dragging
down in vertical split-screen because navigation bar inset was not
included.
This CL sets override inset value as a difference between corresponding
content area dimension and screen dimension.
Bug: 27970692
Change-Id: I5bd16077a7deb039516bc9e11aa58315f809455a
When passing tempTaskBounds != null but tempInsetBounds == null,
we ended up using the stack bounds to calculate the insets, which
is really wrong. First fallback onto tempTaskBounds, and then the
stack bounds.
Bug: 27887505
Change-Id: I66ee0da1415a67af824f4c63b56644d590728813
When loading roots for the first time, we're okay using any cached
data from the system, but if the locale changes we need to
force-refresh everything.
Now that we're always using the system cache, we have a nice strong
signal for "empty" versus "not cached" results, so we don't need to
wait around for the first loading pass to finish.
Add logic to invalidate system cache when locale changes, and fix
locking bug.
Bug: 27977906
Change-Id: Ic50083eff360bea887799583f6c9f02c129eec91
If we intersect each window in the application with
our screenshot bounds we will end up reduced to the bounds
of the smallest window. Modify logic to just check for
intersection without modifying the bounds.
Bug: 27996291
Change-Id: Ib0ebb6bd02a313f67f1562dabcfb394efa8f16cf
- When SysUI crashed, make sure state is up-to-date
- When divider gets invisible, update state because animations
won't finish
- Make sure to keep mMinimizedDock up-to-date in all cases, even
if docked stack is already gone.
- If docked stack is going away, reset minimized state
- Disallow undocking when minimized.
Bug: 27588187
Bug: 27486464
Change-Id: I6ea48562fae3a8df038a690a488580d758681370
Add a shell command for switching webview implementation so that this
can be done automatically - without interacting with a Dev Setting.
Bug: 27540566
Change-Id: I3c4acaa1b8f4ba24c637ef8a1d48cc7b2616bd91
If a DimLayer becomes fullscreen while it is animating out,
then it will not be the shared fullscreen dim layer. However,
state.continueDimming will be false (as we are ending the Dim),
so around DimLayerController.cpp L191 we will identify it as
fullscreen, skip animating it for now, and not set fullScreenAndDimming
to the index (because continueDimming is false). fullScreenAndDimming
will be -1 so we will now animate the dimmer at index "fullscreen"
this will simply be the last fullscreen state we found, which would be
fine if the state we had skipped was the shared fullscreen dim layer,
but it wasn't. Ensure that we identify the layer as fullscreen and the
shared fullscreen dim layer.
Bug: 27775427
Change-Id: I49d4f59bb09af6a7e5bd666e499be1c7e11ee766
We need to leave space WINDOW_LAYER_MULTIPLIER between Z-order
adjacent normal windows, for things such as Dim Layers, etc. The
existing logic was breaking DIM_UNDER DimLayers in DockedStack. Consider
two normal windows, the second on top and with a DIM_UNDER. If we are
docked we will have restacked all the docked windows at HighestLayer+1
HighestLayer+2, etc...and so our second normal window is only one higher
than our first one. So when we put a dim under the second window
we end up with the same layer and the output is undefined.
Bug: 27721903
Change-Id: Ic27e0a10da2d1ab4a6058e0755ad4409b29527eb
This follows up to my previous CL [1], with which we changed global
hardware key combinations regarding how multilingual user can manage
multiple keyboard layouts / input methods. Now we offer Meta-Space to
rotate input method (subtype), while we offered Shift-Space to rotate
hardware keyboard layouts previously.
One thing that is lost during above transition is an indication when the
such a key combination takes effect. Actually there was a toast that
shows new keyboard layout name, which is now lost.
With this CL, we bring back a toast so that we can show the new input
method (subtype) name. Note that the toast will be shown if all of the
following conditions are met.
- The input method (subtype) is rotated by a hardware key combination.
- IME window does not have IME_VISIBLE bit. Otherwise, showing a toast
is likely to cause UI overlap with the current IME's window.
[1]: I4005692215edfcf8bed3e86b1e07000148f986f5
ae61f7118a92e097e854c840d5726c0920f5db0e
Bug: 27547054
Change-Id: If3fe17adbffe4c1125783fc77fed3cfe78fc7933
Move more code from WebViewUpdateService to utility classes (methods
handling settings and uninstalling/enabling/disabling packages) to be
overridden during tests.
Also rename system utility class.
Bug: 27635535
Change-Id: If49999fba4fd0962f103f389898fa5ddf19365bd
When the system is shutting down or the screen is going to be off, <Standby>
message will be broadcasted if and only if the setting variable,
Settings.Global#HDMI_CONTROL_AUTO_DEVICE_OFF_ENABLED, is enabled. This change
will make the shutdown case to be checked with the setting properly, too.
Bug: 27781559
Change-Id: Ia6605d6b5627ab1ff67285d72846b618a09548bc
