automerge: f12d0233

* commit 'f12d0233':
  Changes made by intelliJ 14.1

* commit '221d7320':
  Changes made by intelliJ 14.1

automerge: 4e474160

* commit '4e474160':
  Changes made by intelliJ 14.1

automerge: 712572d4

* commit '712572d4':
  Add BLAS intrinsic.

* commit '41c93ffe':
  Add BLAS intrinsic.

Change-Id: I95ddc46cb3f6217d2ead1091fd47450389544324

* commit '7131a7d6':
  Disable color view animations when stable insets change

* commit 'd245ad24':
  Disable color view animations when stable insets change

* commit '024fd0c6':
  Disable color view animations when stable insets change

Prevents color view from showing up on phones when
the orientation changes to landscape. Previously, the
animation was only prevented when the stable inset of a
bar became nonzero; now we disable animations whenever
the nonzeroness changes.

Bug: 19353466
Change-Id: I31b4103fe984d158a98cd446ac2ddbe15a408e49

* commit '2aa2672d':
  Add missing <sys/file.h> include for flock.

* commit '627396ac':
  Add missing <sys/file.h> include for flock.

* commit '5d8f2491':
  Prevent leaking surfaces from exiting windows

* commit '2a005f6f':
  Prevent leaking surfaces from exiting windows

Change-Id: I0c66c03aeb4df614f7880a830b95c40f43f804db

* commit '0a786f5f':

automerge: f27b9850  -s ours

* commit 'f27b9850':
  Import translations. DO NOT MERGE

* commit 'f27b9850':
  Import translations. DO NOT MERGE

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

* commit '58524b2a':
  Register DDM handlers at the beginning of main method.

* commit 'e7e92381':
  Register DDM handlers at the beginning of main method.

AM would set the exiting app to be invisible twice by calling
setAppVisibility(). If the screen is turned off during these calls,
the window surfaces of this exiting app won't be destroyed.

The flow:
 1. Screen is on
 2. App A is finished
 3. AM calls setAppVisibility() token=App A, visible=false
 4. WM sets a dummy animation to App A
 5. WM marks App A's wtoken.inPendingTransaction=true
 6. Screen is turned off
 7. AM calls setAppVisibility() token=App A, visible=false
 8. WM calls setTokenVisibilityLocked() directly (screen is off)
 9. WM sends app visibility to App A's client (ViewRootImpl)
10. WM clears the dummy animation from App A
11. App A's client calls WMS.relayoutWindow() to be not visible
12. WM sets App A's window mExiting=true but not destroy its surface
13. App A's window surface leaks...

Note:
a. The call in 3. is from ActivityStack.finishActivityLocked
b. The call in 7. is from ActivityStack.resumeTopActivityInnerLocked
c. In 10., App A won't get the real animation while screen is off
d. In 12., App A's inPendingTransaction=true; WM takes it's animating
e. mExiting won't be cleared because App A has no animation to
   trigger WindowStateAnimator.finishExit()

After applying this patch, WM would destroy the surface in 12. of the
above flow.

Change-Id: I18b79ba96695ec80d57a85dc15cf92a9e7d3a6ef

am 83c804be: Merge "Prevent duplicated registration of OnComputeInternalInsetsListener" automerge: efd9abb7

* commit '83c804be':
  Prevent duplicated registration of OnComputeInternalInsetsListener

automerge: efd9abb7

* commit 'efd9abb7':
  Prevent duplicated registration of OnComputeInternalInsetsListener

am 88a9a2a4: Merge "Support for faster brightness response to light changes." into lmp-mr1-modular-dev

* commit '88a9a2a4':
  Support for faster brightness response to light changes.

* commit '12c9e498':
  Changes made by intelliJ 14.1

Bug: 18572096

Change-Id: Ic9448db672b036779d16883f3476249cea45d97a

Compiler initializes RuntimeInit during compilation and stores an
initialized version of the class in oat file. Same thing happens to
DdmServer which handles DDM packets in JDWP thread started during JVM
creation. This means that after the creation of JVM all
DDM packets are handled by DdmServer.dispatch and since it's already
initialized during compilation it has all framework related handlers
already registered. If a packet arrives before AndroidRuntime.startReg
is called then framework native methods are not yet registered and the
processing of the packet fails with UnsatisfiedLinkError.

To fix this problem the registration of framework related DDM handlers
is moved to the beginning of ZygoteInit.main and RuntimeInit.main. This
means that the handlers won't be registered until main method is called
and that's guaranteed to be after AndroidRuntime.startReg is called. It
also guarantees that DDM packets will be properly handled as soon as
Java code is executed.

Bug: 18081539.
Change-Id: I9c674f53f3f62d58c46886e0b60698182e08f0c3

* commit 'aee7f64c':
  Remove code that sets user.* system properties.

* commit 'b4a5c04c':
  Remove code that sets user.* system properties.

This has been disallowed by the SELinux for several years now,
so can safely be removed. Given that saveLocaleLocked is
simplified quite a bit, we can now inline into its only caller.

bug: 18910417

Change-Id: I18251f77e4a25a0e7ecda8e85a9b3fcdc2dc7b05

am 5136791b: am 599c1042: Accessibility: Ensure fresh accessilbity focused and input focused nodes. automerge: 27ad2e95

* commit '5136791b':
  Accessibility: Ensure fresh accessilbity focused and input focused nodes.