Some apps request the low-latency Tx paths for voip.
eg. Skype on hlte is unable to use the mic as it's
asking for the low-latency-record path.
Adding in the low-latency paths solves this issue.
Change-Id: I0cf30ef334135045e471998b5f0d3ee9f1bfd4ac
- Issue with returning a valid device descriptor
since BT SCO is not defined in IOProfile.
- With Android-Q changes, first attempt to retrieve device
descriptor from the avaiable HwModule may fail due to
address and encoded format conditions.
- Further device descriptor query is based on IOProfile
with devices defined in audio_policy_configuration.
- This change adds BT SCO to IOProfile.
Change-Id: I52225070e97dd702f965ca5dbb5db9d128df1faf
Bug: 37492580
Test: dumped the effectFactory state and check it was unchanged
$ adb shell dumpsys media.audio_flinger | sed '/Clients:/q'
Signed-off-by: Kevin Rocard <krocard@google.com>
* Rename klte-common -> s3ve3g-common
* Drop fingerprint related blobs
* Drop camera shim, we do not need it
* Drop CameraWrapper to msm8226-common, as all msm8226 devices uses it
* Drop broadcom NFC
* Add buildable libpn547_fw.c, libpn547_fw_pku.c, libpn547_fw_platform.c dumped from stock S III Neo sources
* Update audio configs with stock S III Neo ones
* Update power_ext for S III Neo
* Drop broadcom WIFI for Qualcomm WIFI as we got a Qualcomm WIFI chip
* Drop broadcom bluetooth as we goot a Qualcomm bluetooth chip
* Update partitions for S III Neo
* Update rootdir for S III Neo
* Update overlay for S III Neo
* Update liblights path for S III Neo
* Update deviceperms for S III Neo
* Drop consumerir as we do not got an IR blaster
* Update TWRP files for S III Neo
fw/b changes in Oreo cause some USB audio devices
which were previously recognized as AUDIO_DEVICE_OUT_USB_DEVICE
or AUDIO_DEVICE_OUT_USB_ACCESSORY now to be recognized as
AUDIO_DEVICE_OUT_USB_HEADSET (0x4000000), causing this error:
AudioPolicyManagerCustom: setDeviceConnectionState() could not find HW module for device 04000000
BUGBASH-2398
Change-Id: If1f6c760e28a2daeb3855c86fc561c7e5e85f0bf
* The updated audio HAL sources (for instance 8.0.0_r33) use
the formats directly through the pcm_format_from_audio_format
inline functions to resolve and validate provided formats,
however in our case the formats include values outside
of the allowed AUDIO_FORMAT_PCM_... values and fail
* Crash situation was happening upon 3.5 Jack plug only
Change-Id: I4b613c25ea7fd202a434c18c2fdd06e55a57c456
Signed-off-by: Adrian DC <radian.dc@gmail.com>
* What Qualcomm was trying to fix was a real problem, it just created
even more problems which are incredibly difficult to solve such as
underruns and even broken apps (Loop reader, etc). Do it Google's
way and forget it- it's a non-issue with offloading anyway.
Change-Id: I0e9194c85606745e801630e64e8e5d0c8b8dc022
* Recordings with the Voice Recorder app were very low, increase to
match that of stock mixer_paths.xml from T-Mobiles NH5 release.
Change-Id: Ia0d036e5c8bad00a8ae99e93b4ce8a60cddb34e1
* Samsung device names are custom and require a mapping.
* Do the mapping from the CM HAL expected paths to Samsung paths
in mixer_paths instead of in code.
Change-Id: I399bdc53a7f098030859e91ec93038ea9378fb95
* There's a standard way to do this by configuration without linking a
custom library for no real reason.
Change-Id: Iee7cebc1fad51b4a340e8a9fb0f7c10f6bd7b15b
