-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug on 405,406,The sound source is incorrect #93
Comments
The audio code needs some attention.. |
If you know how to fix it, please do :) |
I'm sorry, as I said before, I'm not a professional in this field.The problem I mentioned is perhaps a more common one.The APP in the project below has an option to repair the call speaker in the settings. I think her role may be to solve this problem, and I don't know if it will help you. |
Some new audio code has been implemented. Let's see if that helps. Please test the upcoming release. |
Unfortunately, bugs still exist in version 407. |
Maybe it has something to do with the equipment I use. The phone I used was the redmi K40, also known as the poco F3, which is Xiaomi's device codename Alioth.It has an upper speaker and a lower speaker, and the upper speaker is combined with the earpiece. It is possible that the dual speakers are causing the problem. |
@SunDaSora hard to say. More debugging needs to be done. |
The previous connection failure bug has been fixed, but now there is a new problem.When calling or being called on some devices, the ring tone is normal, but the sound source is not correct after connecting.
My Redmi K40 will use the speaker to play the conversation.It's like a video call, not a voice call.
On the other phone used for the test, whether the camera was turned on or not, his voice came from the earpiece.
I think it might be possible to manually add a switch to switch between the speaker and the earpiece, or automatically switch the sound from the speaker or the earpiece depending on whether the camera is on or not。
The text was updated successfully, but these errors were encountered: