search

twilio / audioswitch

An Android audio management library for real-time communication apps.
Apache License 2.0
160 stars 49 forks source link

Car play show wrong caller id and also audio doesn't end on call end, required to force close the app #161

Closed softsan closed 1 month ago

softsan commented 2 months ago

Before filing an issue please check that the issue is not already addressed by the following:

Please ensure that you are not sharing any Personally Identifiable Information(PII) or sensitive account information (API keys, credentials, etc.) when reporting an issue.

Describe the bug In continuation of this bug I found another issue related to car audio. I am using it with the voice sdk android for my voip calling app. When an incoming call came in, it shows binary number like 1000000 as caller id on car dashboard while on my mobile app it shows correct caller id. so my caller id is likephone number - name or some time name - team name(both strings). Also when call is ended from app it still ongoing on car bluetooth and it only ends when i force close the app. So any resolution on this?

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior It should end the call from car bluetooth without force closing app. Also it should show correct caller id instead of 100000 number.

Actual behavior It shows wrong caller id with some binary number like 100000 and also call is not ended on car dashboard when ending from mobile app.

Application Logs

AudioSwitch Version

Android Device (please complete the following information):

Screenshots

car_bt

Additional context Add any other context about the problem here.

softsan commented 1 month ago

Any updates on this? or workaround?

afalls-twilio commented 1 month ago

@softsan Thank you for the bug report, we will get back to you shortly when we have a chance to reproduce it.

ocarevs commented 1 month ago

@softsan AudioSwitch currently does not support any custom bluetooth actions, we only trap connection and disconnection actions. At this point this is not on our timeline, but it's not to say that we could not add support for custom actions at later date.