This CL adjusts the Tangor tuning to handle recent
code changes in the counterpart in AOC. With the
tunings, the behavior is identical to prior to
the changes in AOC.
Bug: 295551854
Test: Manual testing in calls on TangorPro.
Change-Id: I59f5753e972241e3f24f3e142daad8cbe81c5cf2
This CL extends the APMg3 AOC control to handle more profiles
to a scheme which is tailored to also handle phones
Bug: 295551854
Test: Manual testing in calls on TangorPro.
Change-Id: I17046fb373f8c1e7c21d52bc016487f6714603b7
This CL updates the APMg3 tunings to version 12.
The changes performed is to increase the AEC transparency as well as
increase the robustness to echoes.
The tunings have been verified by audio labs in TPE and STO and documented in
https://docs.google.com/spreadsheets/d/1kL9XqE406CGI_LaggCmI9mJ1DUuelmvFMI4FksYEKJA/edit?pli=1#gid=674561254https://docs.google.com/document/d/17FBTzIA7fuGnkS_fPvE4MN2sB_FKM2EPelPeBvTamzE/edit?tab=t.0#heading=h.h0idgem10n71
The sha256 checksums for the tuning files are
uplink_tablet_stereo_config.pb: e7c4b95c28f87b4f62bbf320a244df7bd26f2075c3646a3ba962c746d409fa33
uplink_dock_config.pb: 7ac91df3386dd26c8bafec4bb5a52917507b4baf13934aec4262aa2fc2be2123
The tuning files are also available in the google3 folder
third_party/apmg3/rtc_tools/dsp/tunings/tangorpro
(being landed as part of google3 cl/588934009)
Bug: 295551854
Test: Manual test calls on Tangor using Meet. Lab test performed by both STO and TPE labs
Change-Id: Id6bf7439a6c02c866a06f47fad239c0fb3cef632
This CL updates the APMg3 tunings to version 11.
The changes performed is to remove any signal level gains applied in APMg3 in AOC
for the headset usecase when the AEC is off. This eliminates the issue of 25 dB
gain being applied when headsets are used causing some headset audio signals to be
saturated.
This is a correction of the CL
https://googleplex-android-review.git.corp.google.com/c/device/google/tangorpro/+/25019613
which both included an active gain for headsets when the AEC is off.
As a safety precaution, and to allow easier spotting of such issues, the CL also
explicitly sets the gains to 0 dB also for the other headset tuning (before it was
just deactivating the gain application for that)
Bug: 309517292
Test: Manual test calls on Tangor using Meet.
Change-Id: I4f29cd780fa6ca52df543387546d2a4b4b161139
This CL extends APMg3 tunings for the tablet, dock and headset usecases with counterparts where the AEC is off.
Bug: 301568974
Test: Running CTS test suite verification. Manual testing in calls on Tangor.
Change-Id: I87fd24ba084691c238f5c07272208049acaf2e5d
note: add smartfeature.gstf that only used for Hotword
pipeline in AoC which is sharing to chre usage too.
On WHI_PRO
CHRE PDM Gain(gain=158)
CHRE AEC Gain(gain=-42)
CHRE SRC AEC Timeout(timeout=0)
This table also contains hotword gain control as
(Undocked)
Non Eraser gain (gain=220)
Eraser Pre gain (gain=220)
(Docked)
Non Eraser gain (gain=356)
Eraser Pre gain (gain=170)
Eraser Post gain (gain=186)
Test: end-to-end verify by CHRE
using aoc_audio_cfg to query gain as below
adb shell aoc_audio_cfg hotword_get_non_eraser_gain
adb shell aoc_audio_cfg hotword_get_eraser_post_gain
adb shell aoc_audio_cfg hotword_get_eraser_pre_gain
Bug: 271078701
Change-Id: I4e3416af224742d939c0928c6623705a01924581
Updating the Waves tuning to T6K6 REV25
(Google_T6K6_REV25_T6-v19_K6-v17_20230107_43-Madonna)
Bug: 263304645
Test: Build only
Change-Id: I6ad98e2159241573f9e99101b8efa201d0020eb1
Updating the Waves tuning to T6K6 REV18
(Google_T6K6_REV18_T6-v13_K6-v10_20221213)
Bug: 262400333
Test: Build only
Change-Id: I08439e8452adc0ab44305695cadfe92c0c20df96
Change notes:
1. "audio_platform_configuration.xml" change the sampling rate
from 48kHz to 32kHz. details ref to b/253552165#comment3
2. "HEADSET_iS900_Nest_T6+K6_Oct18.dat"
Based on C10's headset tuning table adding back the following
K6 cases from Oct14 headset tuning table:
T6+K6: idx 0x6B
SWB(32k)
l HEADSET-DOCK_SPEAKER-VOICE_GENERIC-SWB (AEC on, NS on)
l HEADSET-DOCK_SPEAKER-RESERVE2-SWB (AEC on, NS on)
l HEADSET-DOCK_SPEAKER-RESERVE1-SWB (AEC off, NS off)
l HEADSET-DOCK_SPEAKER-CUSTOM1-SWB (AEC off, NS on)
l HEADSET-DOCK_SPEAKER-CUSTOM2-SWB (AEC on, NS off)
FB(48k)
l HEADSET-DOCK_SPEAKER-VOICE_GENERIC-FB (AEC on, NS on)
l HEADSET-DOCK_SPEAKER-RESERVE2-FB (AEC on, NS on)
l HEADSET-DOCK_SPEAKER-RESERVE1-FB (AEC off, NS off)
l HEADSET-DOCK_SPEAKER-CUSTOM1-FB (AEC off, NS on)
l HEADSET-DOCK_SPEAKER-CUSTOM2-FB (AEC on, NS off)
3. "C10_BLUETOOTH.dat" just following the latest C10's BLUETOOTH.dat
Bug: 253541689
Test: Acoustci verified
Signed-off-by: Carter Hsu <carterhsu@google.com>
Change-Id: I5462be02c105aca4c54415b914e4104e1fefb5aa
This reverts commit de07b38b16.
Reverting this change until we find the optimal gain setting for the
hotword pipeline.
Bug: 215251713
Test: build
Change-Id: Ica6c59ec4c413c7ad3aed301509f3ef914606bea
Updating the gain settings for 'eraser_pre_gain' and
'non_eraser_gain' to 35.6 dB through the 'smartfeature.gstf'
file generated by the bluenote tool.
Bug: 215251713
Test: Verified the new gain settings on T6.
Change-Id: Iee4037541a2aa69188c7c598ab2aff4d9b70c104
based on two sources:
1. 52e030ecef8a2debcd0a7cebb0b2cddc50e8e4e6
(ChangeId: Ieba6a75fe45595592c61dc5ad4e0c723adccaf35)
2. 3164f3d31b1197f305d968027f2e6f18663f1382
(ChangeId: Ic517f1cd5462f3653de3742834ec251362e7849d)
No-Typo-Check: based on above commit
Bug: 220073297
Change-Id: I244f73dc8485045e1bc4605a2701a1e4d32139b0
