Fixed runtime linkage problems for libOpenSLES and libOpenMAXAL

Libraries libOpenSLES and libOpenMAXAL depend on liblog but Android.mk
doesn't specify it.  Native app links libOpenSLES or libOpenMAXAL
may fail with the following error message (taking
$NDK/samples/native-media as an example)

E/AndroidRuntime(  824): Caused by: java.lang.UnsatisfiedLinkError:
Cannot load library: link_image[2260]:    82 could not load needed
library 'libOpenMAXAL.so' for 'libnative-media-jni.so'
(mips_relocate_got[1804]:    82 In 'libOpenMAXAL.so',
can't locate symbol __android_log_assert)

The root cause is that both libOpenSLES.so and libOpenMAXAL.so depends on
liblog (containing the offending __android_log_assert) but Android makefile
doesn't specify it.  The reason that linker doesn't complain about it
is because "--gc-sections" causes linker to "garbage-collect" which
removes unused (in this case "invisible") functions __assert/__assert2
in both shared libraries.  Unfortunately, due to a bug (recently fixed
in 2.22.52 http://sourceware.org/bugzilla/show_bug.cgi?id=13811), linker
forgot to also remove references to dead function __android_log_assert
called in __assert/__assert2.

In theory this should affect all Android devices for native app linking
libOpenMAXAL.so or libOpenSLES.so, but it seems at this moment only MIPS-based
device is affected.

Fixed Android.mk to make it explicit.

bug: http://code.google.com/p/android/issues/detail?id=30179
related CL: https://android-review.googlesource.com/#/c/36302/

Change-Id: I61655a77d85f57cf103f9ac51505dc3d58f7c866
Merge "Fixed runtime linkage problems for libOpenSLES and libOpenMAXAL"
am 7a789817: (-s ours) Merge "Fixed runtime linkage problems for libOpenSLES and libOpenMAXAL"

* commit '7a78981743646776bb96a80a45900e53d2cc6ab8':
  Fixed runtime linkage problems for libOpenSLES and libOpenMAXAL
Improvements to camera metadata handling.

- Cleaner interface to get/find
- Adds delete entry, an expensive O(n) operation
- Adds update entry, which is O(n) sometimes
- Minor bugfixes:
  - Keep sorted state when appending empty buffers
  - Misspelling of camera_metadata_type_size in header
  - Missing entry in type name array

Bug: 6243944
Change-Id: I316507d6adcc22aff6e7c464c6c484f31ef1510d
Camera: Minor revision to metadata tags, many more enum definitions.

- Remove some tags, adding a few others
- Add enums for all current tags that need them for their values.

Bug: 6243944
Change-Id: I69085eaad68ef39f7047e93570b4591165cca308
Reconcile with jb-release nakasi-factoryrom-release

Change-Id: I247268c7e5086e0d117c0ae133731f0353cd492e
Merge "Improvements to camera metadata handling."
Merge "Camera: Minor revision to metadata tags, many more enum definitions."
Camera: Update to latest metadata definitions

- Revamp resolution information
- Add sizes for shading, geometric correction map
- Add hyperfocal distance
- Add sensor physical size
- Remove unneeded color modes
- Add scene, effect modes
- Add some missing enums for other parameters
  - Facing
  - AF modes
  - Available scene modes

Bug: 6243944
Change-Id: Ia5c9448ef2857f8dd39488810030b4e548711194
Camera: Add opaque user pointer to camera metadata buffer

This is useful for associating a metadata buffer handed off to a third
party with its parent object, when the buffer is returned.

Change-Id: I7e19708bb3adf4da26fc6101e78c276477276608
Camera: Add clone buffer, make type names public

Clone metadata buffer allows for straightforward duplication of
existing buffers; type names are useful for debugging code.

Bug: 6243944
Change-Id: Ibf70f4e3bcf49d6c772bba18a577e2673f2b9213
am ab0deb6c: Add parameter for set visualizer latency

* commit 'ab0deb6cedd635d138e3d4f0d2c0623fa7f62e46':
  Add parameter for set visualizer latency
am 63a6d6f7: am ab0deb6c: Add parameter for set visualizer latency

* commit '63a6d6f7b1a0ae600d2008d249991b402d3be96b':
  Add parameter for set visualizer latency
Reconcile with jb-release

Change-Id: If0d3b223253e967731cf795e773045dc6d9affd2
am 5b1a974d: Reconcile with jb-release

* commit '5b1a974d08aa0bfa25d890026b38073375bdbf55':
Camera: Add metadata field ANDROID_JPEG_MAX_SIZE

This is used for communicating how large JPEG buffers must be to the
framework.

Bug: 6243944
Change-Id: Ib296961c4033535cdcd9baf297d440a31cf94d84
Merge "Camera: Add metadata field ANDROID_JPEG_MAX_SIZE"
Camera: Add LOCKED values for AE/AWB modes.

Bug: 6243944
Change-Id: I52e842d568790e8ac0d9c231507e865aad58601b
Add mono <-> stereo upmix and downmix routines

Change-Id: I3d960fb27fd3440f903333903c0dbf2ab59d3b56
comments on FX tags

Change-Id: Ic22c12c34303988c4a1616e49822859b975fe6c4