-
Notifications
You must be signed in to change notification settings - Fork 665
No incoming audio in phone calls [Razer Phone/cheryl/potentially all CAF devices] #12
Comments
Manually extracting the following files from the razer DP1 image (injecting their respective vdex's) This means MSM8996 fixes don't help in the MSM8998. |
Getting my Razer phone tomorrow, let's see then, subscribed to issue. |
As a follow up to last night's comment, trying to inject the Apks corresponding to Qcomm RIL QtiTelephonyService, QtiSystemService, Qcrilmsgtunnel from the stock rom into the GSI didn't work either. |
As an update, @TheCrazyLex and I have tried by adding the flag "AUDIO_OUTPUT_FLAG_FAST" to the primary output mixport inside vendor's audio_policy_configuration, still with the same results |
New update. I've delete the Razer signature from the files QtiTelephonyService, QtiSystemService, Qcrilmsgtunnel, and resigned them with the system signing key. Now files are installable and services run like normal. For the specific case of Qcrilmsgtunnel, I've faced the issue that it was missing a library from HIDL, but that file is indeed present in the system after comparing the tree output between GSI image and Razer image. Concerned, I decompiled the apk in question and changed Now, I moved the missing libs back to the system to check if audio worked, and this is what happened: From the log, we can extract the following 2 errors: Final thought: I'm done :) |
I've fixed it. I'll write up one last comment with everything needed to reproduce the fix on any device. |
Check out this thread I've made to bloat this issue less: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/treble-qualcomm-device-call-audio-check-t3774818 |
Some investigations about the always-on-speaker mode: |
The same change without actually changing audio_policy_configuration.xml: |
Add statusbar height to cover the notch on few more devices
Logcat and dmesg seem okay.
Tried changing the Dialer app to Google's stock one, didn't fix the issue.
Also tried re-routing the audio from the earspeaker to the actual speakers, and to Bluetooth headset, but didn't solve the issue. Only sound that comes from them is a loud 'beep' when the call ends.
3rd party VoIP apps like Telegram or WhatsApp have no issues at all with in-call audio.
May need custom audio re-routing inside the mixer_paths?
The text was updated successfully, but these errors were encountered: