Xamarin.Form can't make OutBound Call with SpeakerPhoneOn on Android 12&13

Universal Camera 276 Reputation points
2023-03-05T07:32:09.08+00:00

I was chatting with Microsoft Support regarding Xamarin AudioManager. They encouraged me to post the question on this Forum. I reminded them that I have been reprimanded by @Rob Caplan and was trying to follow his instructions without success. I don't have ADMIN privileges.

https://learn.microsoft.com/en-us/answers/questions/1164305/xamarin-form-make-outbound-call-with-speakerphoneo?comment=question#newest-question-comment

please someone provide a solution for Android 12&13. I have posted many solutions for Android 9&10&11 which work great!!

Developer technologies | .NET | Xamarin
Developer technologies | .NET | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Rob Caplan 6,127 Reputation points Microsoft Employee Moderator
    2023-03-05T20:27:50.9533333+00:00

    Repeating the same question isn't going to get you a different answer.

    We cannot help you with Android telephony issues on Q&A. Leaving out half of your problem description--that it is specifically about calling AudioManager from within telephony events--will not change this.

    If you want Microsoft's help with your problem with interactions between Android's telephony stack and its audio stack, you will need to open a support case. It is beyond the scope of what we can help with in Q&A.

    Create a new Xamarin Support Request

    Select Developer Tools / Xamarin / Class Libraries and Runtime / Android Platform Libraries

    If you open a support case we can help you narrow down the issue, but the problem appears to be with Android API and not with Xamarin API. If there is a bug here it would need to be addressed by Android and not by Microsoft.

    I'm not sure who you talked to, but it wasn't anybody in Xamarin support. I suspect you posted a development question on Microsoft Answers, and they forwarded you to Q&A because Answers doesn't cover technical questions. They were not addressing your problem specifically.

    If you open a case through the link I provided and with that path it will go to the Xamarin support team, and that team will be able to investigate the problem. Again though, it sounds like something that would need to be addressed at the Android level not in Xamarin.

    --Rob

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.