Skip to content
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

web-speech-api example does not use microphone input from bluetooth source when connected #283

Open
daveanderson88 opened this issue Oct 10, 2024 · 0 comments
Labels
needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.

Comments

@daveanderson88
Copy link

What information was incorrect, unhelpful, or incomplete?

When testing the "Phrase matcher demo" of the web-speech-api,
https://github.com/mdn/dom-examples/tree/main/web-speech-api#phrase-matcher-demo
On an Android device with the Chrome browser,
When a bluetooth headset is paired and connected to the device, it does not use this bluetooth mic as expected:

What did you expect to see?

Observed behaviour:
Audio input is still routed to Chrome via the on-device mic.

Expected Behaviour:
Audio input should be routed to Chrome via the connected bluetooth mic.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

Other observations:
Audio input is routed via the connected bluetooth mic for phone calls.
Audio output works as expected and is correctly routed from the Chrome browser to the bluetooth headset spekers.
Audio input works as expected when using a wired headset - the microphone from the wired headset is used as audio input when conected.

Android version: 14; SM-G556B Build UP1A.231005.007
Chrome version: 129.0.6668.100
Headset: Jabra Evolve 65

@daveanderson88 daveanderson88 added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.
Projects
None yet
Development

No branches or pull requests

1 participant