This attempts to reland previously reverted CLs [1][2] due to an
unexpected regression (Bug 27824691).

The Bug 27868748 we want to address by this CL is that currently
InputConnection#finishComposingText() can be called on the root view's
Handler no matter what Handler is associated with
ControlledInputConnectionWrapper.  Actually the root cause of
Bug 6789252 is the same, but there we worked around it by not calling
InputConnection#finishComposingText() in certain situations [3].
With this CL we should be able to logically revert that workaround.

This CL also removes redundant IMM#mServedInputConnection.  This is safe
because the following two fields have the same lifetime.
 - InputMethodManager#mServedInputConnection
 - InputMethodManager#mServedInputConnectionWrapper
We do not need to maintain both of them.  This also allows us to use a
strong refecente in IInputConnectionWrapper#mInputConnection instead of
a WeakReference.  To understand why this is safe, we need to understand
how things previously worked, which is as follows:

  1. InputMethodManager#mServedInputConnection becomes non-null.
    -> IInputConnectionWrapper#mInputConnection.get() is guaranteed to
       be alive.
  2. InputMethodManager#mServedInputConnection becomes null or another
     object.
    -> IInputConnectionWrapper#mInputConnection.get() may not be alive.

Since we know exactly when InputMethodManager#mServedInputConnection is
updated, in theory we do not need to use WeakReference here, and
with this CL we do not use WeakReference anymore.  Actually the initial
commit [1] accidentally removed the last strong reference to the active
InputConnection and WeakReference could be null at any time, which was
what we observed in Bug 27824691.

  [1]: I1181e067aa5bedbdf0c7ec1bcec479257aea511c
       afb6558c
  [2]: Ibe94f115e607a198d12ecd3d4e4f91a7d9469c98
       16e2c7b5
  [3]: I66f51da1299532793ef8fa700f35b0811670f235
       4e5184f9

Bug: 27868748
Change-Id: If2a03bc84d318775fd4a197fa43acde086eda442

Making mZenModeController in PSB protected.

Bug: 27101250
Change-Id: Ibb3e66fb59b245aa293bbc32d1c1009ac1a0499a
(cherry picked from commit ac72fc49227fc02a919827a877637df4b0a65cf0)

Merge "If the print spooler gets started onUserUnlock use less of a priority to have less impact on the system." into nyc-dev

Merge "Handle all configuration changes in PrintActivity as it cannot be destroyed synchronously." into nyc-dev

Change-Id: I31783f4aa68742c6a8a4ebe352ab7ec41e21c8fc
(cherry picked from commit eb1cfb75595cf5c7120396d7575bc2beaf4f1967)

Make mQsExpansionEnabled protected in NotficationPanelView.

Bug: 27836776
Change-Id: I35479e990607d6801effd3fa64fd3ffb1f9503dd
(cherry picked from commit 8af5736425d60641268943fe4d7e23a2b7d99c8a)

Change-Id: I311ab683a598426efc4739408be109d766aad721
Auto-generated-cl: translation import

Change-Id: Idba908d9f62c1052034a89f2ff6979d47248fee9
Auto-generated-cl: translation import

Change-Id: I0c9fd440261f12d31c22fbc6bffc0081a90ab187
Auto-generated-cl: translation import

Change-Id: Ida79dc685e550bd3c2765b1e93821a04c4effc52
Auto-generated-cl: translation import

Bug: 27859759
Change-Id: Id4d77d3bd17ae96441960717a4ffe0bf4831562e

* changes:
  Fix config change layout. (Part 2)
  Fixing issue with tasks being laid out with the wrong bounds.
  Launch state/config change audit. (Part 1)

Bug: 27859522
Change-Id: I0e1e578d2d91f7572b0978dbb12ed143acbdf1e1

- Fixing issue where the initial state was not correct after rotating
  the screen.  We needed to update the layout, but that could only be 
  done after the task stack view is laid out.  Now we set a flag to 
  update the initial state of the layout on configuration change, and 
  only scrolling to the front when it makes sense.

Change-Id: I2586b90d1e869708b97bcd1a4446f4d87fa521cc

- When hovering over a drop target, we update the stack bounds, which 
  changes the task rect.  If we happen to pick up new tasks and measure
  them during this point, they will be measured with the wrong rect, and
  once you stop dragging over a drop target, they will not have the 
  right bounds.

Change-Id: I6711152878a4afd48518e01477fd793a4c132648

- Fixing issue with onResume logic being run even when the window focus
  is changing.  This only needs to be run when we are launching into 
  Recents again.
- Removed a bunch of launch state flags that are no longer necessary 
  because of changes to configuration handling.  This reduces the work
  that we have to do on resize, etc.
- Decoupled the resume with the stack-update, which fixes a couple 
  issues where we were updating the layout unexpectedly.
- Fixed an issue where we were not updating the nav bar scrims on 
  configuration change
- Fixing margin start/end regression in header bar
- Fixing small issue with paddings being scaled beyond their base size
- Fixing issue where the clip state was not properly getting reset 
  causing lots of overdraw.

Change-Id: I9aeb191a99ff23807b3f5d905f6480b10157a060

- Fix calculation on which side to apply dimming.
- Fix dismissing parallax logic for new resize handling.
- Remove wrong/unnecessary resizeStack call

Bug: 27738239
Change-Id: Iaac671ca03e19aa70fa779d319b5fe84ff3b40ba

- Set correct clip mode for clip reveal animation
- When moving downwards on a curved path, go down first and then
horizontal.

Bug: 27154882
Bug: 27607141
Bug: 26559810
Change-Id: I0efc073990f7b6a88746ca1e5c68b1fdb0db116d

Bug: 27607141
Change-Id: I146deaa6ce049f27165a236b3aef95b9d4694ced

Fixes: 27823158

Change-Id: Ifed0d6119349662a23899935bfe5f3bacb361617

* changes:
  Implement transition for docking task in recents #6
  Implement transition for docking task in recents #5
  Implement transition for docking task in recents #4
  Implement transition for docking task in recents #3
  Implement transition for docking task in recents #2
  Implement transition for docking task in recents #1
  Show a scrim activity if task is not resizable

Bug: 27264461
Change-Id: Iaea9c34855eb7516993e5c92c1e0369d47e59587

- Use a future to provide the app thumbnail so the app can restart
in parallel when recents draws the bitmap (extremely expensive).
- Don't call startRecents from AM when recents is already running - this
messes up the transition information.
- Make sure to put the task into resizing mode if it needs to be restored
from the disk.
- Some minor fixes for the transition animation spec.
- Add NO_MOVE_ANIMATION to recents flags to prevent wallpaper
flickering.

Bug: 27607141
Change-Id: I7d0c75b88775ab467927b8cf94303ddb60222e7f

bug:27810783

Previous drawColor->drawPaint conversion failed to preserve unbounded
nature of drawColor from old pipeline.

Change-Id: Ifd7a7b9d645f0887e252e48ca95d3195ee31615f