GitLab

- Move all supplicant commands out of jni code in preparation for multi-socket
changes

- Also, clean up some function names to remove the explicit command

Change-Id: Id609ac7df0792fb85b52554d159f22064227c584

Change-Id: Ic237a33038be9a170c1f9128332a8743c57971ed

am 201469f5: am bb7f590a: Merge "docs: Add developer guide cross-references, Project ACRE, round 4" into ics-mr1

* commit '201469f5':
  docs: Add developer guide cross-references, Project ACRE, round 4

* commit 'bb7f590a':
  docs: Add developer guide cross-references, Project ACRE, round 4

Change-Id: I1b43414aaec8ea217b39a0d780c80a25409d0991

* commit '38daf3f1':
  docs: Update App Widgets dev guide size discussion

* commit '38ee0dae':
  docs: Update App Widgets dev guide size discussion

This is mainly an update to match the design guidelines.
See also bug 5555264.

Change-Id: I1c83fb33b7dca412905d21b588c5754d1d3c5cfe

Incorrectly resolved rebase of my previous two commits...

Change-Id: Ie778774deb7ee0979568ca0a8963db2d72bc7a1a

* commit '7e4aa24c':

Change-Id: Ic9251f762e0356c65eff1798cd5897a502d7981e

Change-Id: Ib0389be456755fac24ad130edd0dd091d9acfaae

For historical reasons, messages to the AudioSystem
handler in AudioService have a complex identifier combining several information.
Messages for a particular stream contain the stream type as part of the message type.
This complexity is not needed as the stream messages also carry a reference to the
VolumeStreamState object which contains all necessary information, including the stream type.

Also grouped parameters of MSG_PERSIST_VOLUME message into a single bit field to make room for
further needs.

Change-Id: Ia27af626b3447541e8f9eaceba21389a824d88e2

Old code would detect we were in a retry loop and ignore other active
connections we could share.  We really want live shared connections to
dominate over retrying disconnected ones.

bug:5525764
Change-Id: If93383c52024113eec595b31e46897d1fcabc44c

The previous logic in AnimationSet when starting an animation
ignored the fillBefore behavior of its child animations. This caused
a bug where a delayed AlphaAnimation would automatically cause the
target view to become transparent, even though it was supposed to wait
until after some delay to do so.
The fix checks the fillBefore behavior of each child animation before
concatenating its transform with the transform of the AnimationSet.

Change-Id: I76a2dafbe6dd338dc5281b17612eae87af168d86

* commit '21cb1290':

Change-Id: I123bd5ae61ab8c4f6de1a6640faf0bab89f6aa78

* commit 'c0139281':
  Hide emergency call text if not support it.

* commit 'c892e177':
  Hide emergency call text if not support it.

Currently, you must call initialize() on RotateAnimation or
ScaleAnimation prior to calling start(). The reason is that the
actual pivot point used in calculating the transform is not set
until that method is called. This makes sense in the typical case
where the animation is running on a View and is using values relative
to the size of the View or of its parent. But if the caller sets the
values to be ABSOLUTE types instead, the sizes of the view and the parent
are irrelevant and the call to initialize() should not be needed (and
is not intuitive).

This fix automatically sets the internal pivot values in the case where
the value types are ABSOLUTE.

Change-Id: I74a0e462486efae08aa76e72c0d19d82f2a2677e

Adding a view above the currently displayed child in a ViewAnimator
will cause the displayed child index to become stale, because it is
not incremented to reflect the new position of the currently displayed
view. This fix adds logic to the addView() override to increment the
index correctly.

Change-Id: I9c756ce51a8e8dcbeef8f0e4fbb3704482c21e9d

Change-Id: Ib8a1ba2d12e26cc42a2cec48312a5229bb6d4e8a

* commit 'c296892a':
  Doc Fix: Sensors and Cameras