An accelerated interpolator is used for dismissing when the
the velocity = 0 which can occur with dismiss all or if the
noti is swiped far enough but not fast enough.
There is no duration specified when the noti is swiped far
enough, and the velocity passed in is 0 so the default
duration is used without taking into account the velocity.
This CL alters the code to pass in the velocity so that a
duration is calculated.
Bug: 27864379
Change-Id: Ifac04bb8d1b714c040102fef035d55737c844157
If play() was called shortly after load() and before the load
completion callback, the sample was considered
loaded although the SoundPool was not ready to play it.
Fixed by implementing a more robust state machine for sound
load and play control.
Bug: 22499793
Change-Id: I727e07f842a0adc5225dc248f16bc4a7225a1c8e
The returned descender value for BoringLayout and StaticLayout should
be equal to the font's "bottom" metric in the includePadding case.
Previously, the calculation incorrectly included an addition
mBottomPadding value in some cases (which was an attempt to work
around the case where maxLines was set on TextView but not the
corresponding StaticLayout, no longer the case).
Bug: 27901763
Change-Id: I008c5974b979087725a9bb9104e4771b0caac01c
The real solution is to use ContextCompat, but we can't reference support
library from framework. C'est la vie.
Bug: 27727320
Change-Id: Ib9bcd5f2bdce1996f02fd44877df9ba202b26edc
Not removing the listener causes warning logging, which is especially
heavy when a lot of camera connect/disconnects are happening.
Bug: 27217534
Fixes: 28000512
Change-Id: I4911f27cc0f69301975b110a9b456977050ce5bc
isSustainedPerformanceModeSupported() returns true if the device
supports the mode. It checks for the boolean config
"config_sustainedPerformanceModeSupported" to be set.
Bug: 22864186
Change-Id: I0f9f0bcbb8c02b19f37e9c87570d88e8f78f7992
Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
Up until now, createSession will always do a first render. With the new
embedded layoutlib we might want to actually call objects from the
inflated view before doing a render or even do it between renders.
This allows to avoid the first initial render unless needed.
This CL also fixes a bug that would only happen when multiple render
calls are issued. When scrolling, use scrollTo since we likely want
absolute positions, not relative.
Change-Id: I4b1d8388d7218a8de33e25cd546fd965fcb07dc7
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
Some devices support HDR output for preview in addition to still
capture, so explicitly allow for that in the documentation of
SCENE_MODE_HDR.
Bug: 27313038
Change-Id: I894d7449dc0cfb7353f535db23acd12143590208
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
The correct stream ID is required to be sent along with buffer drop
errors, and LEGACY mode was putting in a placeholder. This would
cause an error in the client-side implementation, triggered by
abortBuffers (Which is the only source of buffer drops from LEGACY).
Bug: 27828602
Change-Id: If3fba7a76f7aa0ff305efa4cce6c225eb720b30e
Add a divider between where system tiles and custom tiles are and
add their app label to them as well.
Change-Id: I8890a7fee54e4c5340bbe95c6e100c58f81ee5c3
Fixes: 27874624
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
RenderNode_Delegate nCreate now takes a reference to this. In the
Path_Delegate, the native_offset call with a destination path has been
removed.
Change-Id: I6332bb4733974b817e8a29eab82e2218fcf942c4
With Ic025c109539c3b59638, selection action mode is always started
when there is a selection. This makes it impossible to extend
selection using selection mode.
This blocks creating action mode when full screen extracted mode is
started with selection, but it's same as MNC's behavior.
Bug: 27988877
Change-Id: I9614cb16373029189bfc098b6c1d353326e6b518
