And also to AudioRecord.
Then log the callerName using MediaMetrics from the destructor.
This can be used to tell whether AAudio or OpenSL ES
or Java created the object.
Bug: 154543374
Test: adb shell dumpsys media.metrics --clear
Test: Run an app that uses audio.
Test: adb shell dumpsys media.metrics
Test: Look for "callerName" in the dump.
Change-Id: I000346e72f581d2e40ef4fd0410b579d2a1224e2
PD# GH-245
Problem:
vp8 play do not smooth
Solution:
modify for add vendor soft decoder
for vp8 decoder
Bug: 149354182
Test: U212
Change-Id: I91c6ba90f7d3edc28d6164ec8cd2a57195d0a7a7
Signed-off-by: Jian Wang <jian.wang@amlogic.com>
Log events from service.
Log start, stop, disconnect and other events.
Log underruns and bufferSize.
Bug: 154543374
Test: adb shell dumpsys media.metrics --clear
Test: run an app that uses MMAP, like OboeTester
Test: adb shell dumpsys media.metrics
Test: Expect to see lots of "audio.stream" events.
Change-Id: I690e5226b695d53d038d644f4438c759e08f9fbb
Destroy sessions in following scenarios:
* when setSecurityLevel fail in openSession_1_1
* before handling mock errors in closeSession
* after releasing offline keySetIds
Bug: 153663446
Test: [Native]MediaDrmClearkeyTest
Test: VtsHalDrmV1_<0|1|2|3>TargetTest
Change-Id: I4357051e0be6daa199c5fc3e7505ce65d982e237
Some system services (e.g. SoundTriggerMiddleware) assume that
whenever they start, the audio HAL is in its default (reset) state.
init.rc scripts tie the lifetimes of the audio HAL and system
processes, but when using stop/start this is not the case, and this
may cause spurious crashes in this case.
stop/start is apparently being relied on in some test infrastructure,
so this change is needed to avoid causing problems for those systems
or false detection of problems, which are not actually present in
production.
Bug: 154029444
Test: Manually verify that the audio HAL is stopped on
'adb shell stop', restarted on 'adb shell start' and that the
system boots correctly after.
Change-Id: Icb6eeddfa48b1a49a4d48baae41f9086eb83a9ca
VtsValidateMediaCodecs and VtsValidateMediaProfiles
are just the GTest of vts_mediaCodecs_validate_test
and vts_mediaProfiles_validate_test.
Bug: 142397658
Bug: 154732221
Bug: 154725134
Test: $atest vts_mediaCodecs_validate_test
$atest vts_mediaProfiles_validate_test
Change-Id: I84ec8ae5ccbcfafb282b653a36e2ad25abdd6b27
Merged-In: I84ec8ae5ccbcfafb282b653a36e2ad25abdd6b27
getMicrophones() should return aggregated mic information
from all HW modules, not just primary.
Also:
- Fix assignment of mPrimaryHardwareDev that should be
first from HW module name and then according to primary output
if no module with name "primary" is loaded.
- Make sure we do not dereference mPrimaryHardwareDev if null.
Note that this should not happen with current rule that a primary module
must be present.
- Implement consistent locking scheme where both mPrimaryHardwareDev and
mAudioHwDevs are guarded by mHardwareLock
Bug: 154772890
Test: AudioManagerTest#testGetMicrophones
Change-Id: I7c9449bb705a6fbebdc0642166e58348d47b7ee8
The python test runs each gtest with various command line options.
Such logic should all be part of gtest for them to be parameterized
gtest.
Bug: 154351999
Test: atest VtsHalMediaC2V1_0TargetAudioDecTest \
VtsHalMediaC2V1_0TargetAudioEncTest \
VtsHalMediaC2V1_0TargetComponentTest \
VtsHalMediaC2V1_0TargetMasterTest \
VtsHalMediaC2V1_0TargetVideoDecTest \
VtsHalMediaC2V1_0TargetVideoEncTest
Change-Id: I8fe666305e198db0869f2c91b7f35fa0560abd9d
std::remove_if will only move elements around within the range it was
handed. In order to have the elements actually removed from the vector,
we need to erase() them.
Caught by clang-tidy:
/buildbot/src/googleplex-android/rvc-release/frameworks/av/media/codec2/vndk/util/C2InterfaceUtils.cpp:219:9:
warning: the value returned by this function should be used
[bugprone-unused-return-value]
(and 3 others)
Bug: 154665437
Test: TreeHugger
Change-Id: I9244baf7d6f46cce4c2d8f66fcf57b19c19d32ab
Merged-In: I9244baf7d6f46cce4c2d8f66fcf57b19c19d32ab
If an optional ID3v2.4 extended header was present, it would be
treated as a frame, causing parse errors. Fix by doing ID3v2.4
per-frame unsynchronization after skipping over the extended
header.
Bug: 154357105
Bug: 151448144
Test: CTS, manual w/ temporary additional logging.
Change-Id: Iaeb8cab866b98dcf97f81d3ade4a1c8d26add3a5
Call various functions after calling AAudioStream_release().
Bug: 154274446
Bug: 154274027
Test: this is a test
Change-Id: Ia0938362502b15a4ae5608f0619e0bc5ce78ca22