The new getIccAuthentication should be used. All callers have been updated
to the new API. Remove the old API in this change.
Bug: b/27360179
Change-Id: I160974d53bb6477666b3e1d457accac45cc06bfc
We need to wait until third-party apps can start before we try
binding to the wallpaper.
Bug: 28166684
Change-Id: I6ef559a667104e830e97da68b437ff592816f6f3
Repeating a 0-duration animation makes no sense. In the case of
battery saver mode, all animators are set to 0 duration, and
repeating the 0 duration animations not only waste battery power
but also potentially produce flickers on screen. In this CL,
0-duration animations are skipped to the end, regardless their
repeat count.
Bug: 25451472
Change-Id: I20f9dc2f0ff9c027782a8363ff4cf4a4d390736c
For pre-N, we have inconsistent behavior between ValueAnimator and
AnimatorSet in the case of calling end() when already ended:
ValueAnimator would start() and immediately end, whereas AnimatorSet
would be no-op. We made a decision to be consistent within Animation
Framework from N forward, which means that AnimatorSet will have the
new behavior of starting and immediately ending just like
ValueAnimator. This new behavior will be guarded by an API check.
Bug: 25601129
Change-Id: I2d952a93d8521c547ec8cde173c80d1d8ead0639
If the thread a toast is shown on is shut down,
the attempt to post the hide message to it's handler
will fail and it will never request removal. If this was
only some application background thread we will also not
receive a death notification. It seems best to use a timeout
to ensure we don't need the clients cooperation, espescially
as toasts can keep the screen on.
Bug: 21693547
Change-Id: I1d6e54ded5b9e2050daedc4d263e2e21fbe69862
Copied relevant DP1 known issues to DP2 section, and noted that
TestDPC was updated for DP2.
See first comment for doc stage location.
bug: 27625537
Change-Id: Iebbd55c946d197db3095f5f4fe6fc2f73f52873d
When starting the "App may not work in split-screen" activity which
is translucent we used to transfer the starting window, and then the
frame was drawn quickly so the starting window from the behind was
removed, leading to a black hole.
Bug: 28094732
Change-Id: I828f0ea8b0465a5a113fd76a82d33177c8faa566
In findDropDownPosition it's entirely possible for width/height
to be -1. If this is so, and the popup is anchored to the right,
we could fail to see that it is offscreen (since we think the width
is -1), and so fail to do our position adjustment to move it to the
left. I think this was previously covered up by window manager bugs
with child windows that requested coordinates outside of their
parent frame. To fix this, we ontinue to pass the same value to
the window manager, but use the width/height we expect to receive
for local layout calculations.
Bug: 28085451
Change-Id: Ia04ca3fcd17ad8819615b5ff42f7923462ce4b42
Dialogs, etc, may appear to not be drag resizing as they are not base
windows. Still though, when they resize we don't want them to enter
in to this mResizedWhileNotDragResizing mode or we will freeze
surface boundary updates and lose the ability to crop them to the stack.
Bug: 26668339
Change-Id: Id603816cf5f33b281f46c7812779ba29a024f34f
When are are docked resizing, just fake
the task bounds as the stack bounds for the purposes
of DimLayers, even if we don't want to relayout the
application interactively we want the DimLayer to keep
up with the divider.
Bug: 28154322
Change-Id: I86e41324cf384f2dceea15cd5e8ddd753dc5bfbd
We were comparing the objects, not the strings, which happened
to work in many cases as they were both the same package name String.
Bug: 26668339
Change-Id: I025d05586cc6c11e788add967c7e6ad916cba276
maybeRemoveReplacedWindows is called when any window
has reported drawing, we have to verify that we have
actually ourselves drawn, before commencing the replacement.
Bug: 26668339
Change-Id: Iabfc2e813989381f9f20f3bb111100911405686b
Prevention of entrance animation for seamlessly replacing windows,
was not working for non child windows. To correct it, we simply bail
from applying the app entrance transition.
Bug: 26668339
Change-Id: I4349e6aef55c3957d81a0a168cf6ac1d7c8866f1
There're two major problems that prevents GnssMeasurement from N-HAL from
delivering to Java-side correct:
1. The size check of HAL-provided GnssData is wrong. So native code rejects all
valid GnssData.
2. The svid's data type is different between HAL-side and Java-side. Therefore
an explicit type casting is required.
This CL fixes those problems, together with a few typo fixes.
Bug: 28169973
Change-Id: Id0c2cc120387970564b840cfcbdcb6f329c7e543
