You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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).The text was updated successfully, but these errors were encountered: