Rename AudioRecordingCallback.onRecordConfigChanged() to
onRecordingConfigChanged() after API council review
Bug 27952000
Change-Id: I362a973781e029bca921181934599dcf60e13136
Replaces deprecated constants with newly added constants in the actual
implementation.
Bug: 27932489
Change-Id: Id54236a05127cd7ce3bf0668c002635fb86489a9
Fix error in audio focus dispatching log: the message value (here
MSSG_FOCUS_CHANGE, which is 0) was logged instead of the focus
value being sent to the audio focus listener.
Bug 25790720
Change-Id: I534ce8d1059c09a52e56c51acd60405ef3c4cda1
Previously ExifInterface saved its tags in the all possible IFD tags via
setAttribute() method even it already knew the right IFD group for those
tags. In this CL, it introduces updateAttribute() and removeAttribute()
methods in order to maintain the internal IFD tags and its values
according to its original EXIF saving states in the given JPEG file.
Bug: 27583378
Change-Id: Ie49163c8c9bdd38b575ccd76938879ccddcd547b
For setBufferSizeInFrames() and related methods.
Bug: 27384290
Change-Id: Ie5decb39d7945f304f57163c5da540cfd01903c7
Signed-off-by: Phil Burk <philburk@google.com>
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
When saving attributes(that it writes JPEG again.), now ExifInterface
generates some uncessary pointer tags which refer to an empty EXIF IFD
group, that makes a warning message by ExifInterface when reading again,
which warns that the value of the pointer tag pointing to is invalid.
Bug: 27583378
Change-Id: Id0170c5644541565c98fe4978284098e6664c395
- In case of giving an argument of the image file name or descriptor,
we created a InputStream at the inside of ExifInterface, close them
properly.
- Developers should take care of closing input streams when they use
input streams since they made those input streams.
Bug: 27636804
Change-Id: I9a3a75b1b55dcb2718a60e14814a04cad939d22c
- Give more explanations on dealing with files failed to process.
- Log and return immediately when handling lost JPEG files.
- Minor fixes in logging.
Bug: 27583378, Bug: 27587980
Change-Id: Id9a3d137e5f173fa0e6313402e5dc482a5efd57c
Prevent developers from using a channelMask that will fail.
Bug: 27721209
Change-Id: I87ad67caedaedf6ed2230165cb1687a2a0b74703
Signed-off-by: Phil Burk <philburk@google.com>
