summaryrefslogtreecommitdiff
path: root/libs/androidfw/ConfigDescription.cpp
diff options
context:
space:
mode:
author winnichang <winnichang@google.com> 2025-03-03 16:28:27 +0800
committer Winni Chang <winnichang@google.com> 2025-03-12 15:08:59 -0700
commit7566a0b9563d65836c7c9ea3dfe728668703805d (patch)
tree2910a156cec7676fc3d2d448c5a05906fb671444 /libs/androidfw/ConfigDescription.cpp
parent9735f28d58ebe77d04c3b770e40d4bd73e70e9a2 (diff)
Decouple ARC and SAD
Couple ARC and SAD causes several issues. 1. Initiating ARC can lead to an extended delay in reporting the "ARC initiated" status, potentially causing failures in HDMI 1.4 certification testing. The specification mandates a response time between 200ms and 1s, but the process of binding with the SAD can exceed this limit. 2. Certain ARC devices might interpret the lack of a timely "ARC initiated" report as an error and consequently produce no audio output. 3. Repeatedly initiating ARC can trigger multiple "request SAD action" commands. This can result in duplicate SAD reports, potentially leading to some SADs being missed or ignored by the receiving device. 4. Devices like the Onkyo TX-NR696, which respond with a "feature abort" message before eventually sending the actual supported SAD, can create a situation where the TV fails to receive the subsequent, correct SAD information. Bug: 366350787 Flag: EXEMPT decouple ARC and SAD Test: adb -s CAB36A2EE24208000724 shell dumpsys media.audio_flinger | grep AUDIO_DEVICE_OUT_HDMI_ -A 100 | grep AUDIO_FORMAT| grep -v 'AUDIO_FORMAT_PCM' or check the Profiles under Port Id: xx "HDMI ARC" under Available Out Devices in dumpsys and local test the audio output Change-Id: Ic9bafd856260c15e441895d69fb1a86468889b0c
Diffstat (limited to 'libs/androidfw/ConfigDescription.cpp')
0 files changed, 0 insertions, 0 deletions