The warnings were being hidden by the use of -isystem to include
frameworks/native/include.
Bug: 31752268
Test: m -j
Change-Id: Ib7227295e7b94c79cdc52e19c71be4066a11cedc
It is related to Change: Id17bea8a6ca7132042b9bfefed398a715c139be7
Fix ANR because of bug of Visualizer.
If lpJniStorage was delete first, callback_data_lock become a invalid value.
At mReceiver.periodicCapture() in CaptureThread, it will lock callback_data_lock.
Thus, CaptureThread will wait a invalid memory forever and visualizer wait CaptureThread exiting and causing ANR.
Signed-off-by: ganxiaolin <ganxiaolin@xiaomi.com>
am: c4e8471ba4
* commit 'c4e8471ba4afb0d2cae0d9e29f5c14b4bbfe4524':
android_media_MediaSync: Do not pass NULL to AString ctor.
Change-Id: Id138df3cfe1ee989d4abf52ae283b63419e7047a
am: a7ad6e912f
* commit 'a7ad6e912f82124b9a7e6f2d14a2ccbae79d16f2':
ExifInterface: Set mPosition in AssetStream with proper values
Change-Id: I59abff01d593647048fe42e7b0dd546f9a68ebdd
Part of media security hardening
MediaDrm was temporarily allowed to
run in either mediaserver or mediadrmserver
while all nexus devices were implementing
support for the native_handle representation
of secure buffers. Now that all nexus
devices support native_handle, the MediaDrm
stack can be removed from mediaserver.
b/22990512
Change-Id: I96a5222f94cd1580ac411de5b48beb44b99cc8d7
am: b9c64cd2c0
* commit 'b9c64cd2c06933eda7ff1e691b80c53a74ff09d7':
Handle API review comments from the council.
Change-Id: I9f082a99d5c8cbce3aaa9708f5f0ea75cc5a9ed6
am: 801d416
* commit '801d4161dd9e872bec73d855d21d030ba39a8b91':
ExifInterface: Fix a bug to return only a JPEG-compressed thumbnail
Change-Id: I4ab59b2b7ced0cf9449fdc780692cfcb707d8df4
* MtpEvent: Remove public constructor since properties cannot be set
directly.
* MtpEvent: Move event constants from MtpConstants to MtpEvent class.
* getPartialObject64: the byte[] must have indices of Integer.MAX_VALUE
at most. Document as such.
* sendObjectInfo: what happens if the transfer doesn’t succeed? How is
the app notified? If there is a reason for the failure communicated,
how does the app find this out? Add docs.
* Add isOperationSupported(int) and isEventSupported(int) helpers.
Change-Id: Ifd80016d2ddd3b66d5c45f6da76b6133f0c9a617
Fixes: 28146379
am: 865cef4
* commit '865cef475dd4b0ffcb4df0dd62cb86d4ce65ab08':
ExifInterface: keep the original metadata data instead of strings
Change-Id: Ie02b5ac90a8dde0389ace4bcae081f8bd4e064a0
This CL makes ExifInterface store the tag values as the original forms
and the format validiation is added that compares the given value and
the data format specificed in EXIF specification in order to keep the
valid tag values only.
Bug: 27583378, Bug: 27614052, Bug: 28075709
Change-Id: If60bbddefe74c4b87b4ce64b5fc79e467e36a5b9
am: 02f9e23
* commit '02f9e23525bd3ae97528041bc0eaf25d43d8fc53':
ExifInterface: return only a JPEG-compressed thumbnail of RAW images
Change-Id: If826f5f7612e06d94c0cf17505bf468851d96faa
SoundPoolThread queue is undersized, bump it up to 128 entries. This
improves the performance of loading camera by unblocking the thread that
asks SoundPool to load sounds. Longer term, an API for setting this
number of entries should be added.
Bug: 28087906
Change-Id: Ie5cea5d11844cf035ca13979c188f2c57a8e333a
If type is MTP_TYPE_UINT128, use MtpDataPacket.putUInt128()
not MtpDataPacket.putInt128() to write data to the packet.
Change-Id: Icb9994e24ac216f3bb07d0a2b3cd7ccf3f8c6f3f
In the MTP spec, the object size is stored in MtpObjectInfo as unsigned
32-bit integer and fetched by the getObjectInfo operation. For the
objects that are more than 4GB, the object size is provided as one of
extra properties, which are fetched by different operation.
The CL adds to getObjectSizeLong hidden method to Java MtpDevice class
so that client code can obtain 4GB+ object size.
BUG=27805369
Change-Id: I8a5b85c8db39734f00e49709c61b271eb48ff33d
Also prefer AudioManager.AUDIO_SESSION_ID_GENERATE over
AudioSystem.AUDIO_SESSION_ALLOCATE, because
AudioSystem.AUDIO_SESSION_ALLOCATE is @hide.
Bug: 27562099
Change-Id: I5924554feb919db7f2390f5b062faedd515421af
And also the following things are included:
- Remove mInputStream.
- Update javadoc accordingly.
Bug: 11224701
Change-Id: I30b4c29ac800ae396fca8f6b2c2c0f68028a44b3
