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

Use AudioManager.registerAudioDeviceCallback to avoid BLUETOOTH related permissions #134

Open
davidliu opened this issue Dec 22, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@davidliu
Copy link
Contributor

The bluetooth permissions are currently only used to get information about Bluetooth devices, and aren't actually needed to connect/route audio to the bluetooth device.

This information can be gotten through AudioManager.registerAudioDeviceCallback since API 23, avoiding the need for these permissions. This is particularly important on API 31 and up, where the BLUETOOTH_CONNECT is a runtime permission (with a rather confusing permission message).

@kletzander
Copy link

What's up with this issue? The library still requires BLUETOOTH_CONNECT permission on Android 31+ in order to route audio to Bluetooth headset, even in version 1.2.0.
WhatsApp, for instance, does not require this permission, but still is perfectly able to use connected Bluetooth headset. This is very unfortunate. Our users rightfully object against requesting this unnecessary permission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants