[BUG] Microphone is muted after granted permission in app settings

[rbuiten]

Describe the bug
When users will not accept the microphone permission the SDK will get a microphone_not_functioning returned from the diagnostic flag listener. This can be possible because the permission is not granted, however we do set the outgoing audio to muted when users do not have granted the permission. After the permission is granted by the user (via settings), we Unmute the outgoing audio. Then the audio state is updated to unmuted, but the microphone is still not working. When users grant the permission or already have permission it works well. So it has something to do with the permission.

To Reproduce
Steps to reproduce the behavior:

• start video call
• check for camera / audio permission
• deny the audio permission
• go to the settings
• give audio permission
• go back to video call
• unmute the video call
• audio should be unmuted and the others will hear you

Expected behavior
We expect that if the user has given permission and the microphone is unmuted the others will hear you

Setup (please complete the following information):

• OS: Android, Pixel 8, Android 14 (but also on other models)
• IDE : Android Studio
• Version of the Library used: 2.5.0

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[lucianopa-msft]

This can be possible because the permission is not granted, however we do set the outgoing audio to muted when users do not have granted the permission.

Probably and implementation detail issue as a permission missing is indeed causes the process to loose the access to hardware mic which can be perceived as mic not working.

Then the audio state is updated to unmuted, but the microphone is still not working. When users grant the permission or already have permission it works well.

This I would be expected behavior IIUC, so I don't think there is an issue in that case.