BluetoothAdapter enable() and disable() fail to work even though app targets lower API level [232107689]

Fixed

Bug

Platform

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

May 11, 2022 10:17AM

* Are you an Android developer?

Yes

* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example SPB5.210812.002).

TPB1.220310.029

* Is this a regression from Android 12 to 13?

Yes

* What OEM Device & model are you using?

Google Pixel 5

* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)

Install the provided app
Click on the Toggle Bluetooth button
Toggling will fail on Android 13 and Android 12 saying that it needs the BLUETOOTH_CONNECT permission which is wrong because the app targets API 30 and that permission should only be required if the app targets API 31 or above
Click on the Request BLUETOOTH_CONNECT permission button
Accept the permission request
Click on the Toggle Bluetooth button

Toggling will fail on Android 13 which is wrong because the app targets API 30. Only if targeting API 32 should it fail.

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions, etc

Runtime Permissions

* What was the expected result?

Bluetooth should be allowed to toggle since app is targeting API 30

* Can you provide the API document where this expected behavior is explained?

https://developer.android.com/reference/android/bluetooth/BluetoothAdapter#disable()

* What was the actual result?

Bluetooth could not be toggled.

deleted

Restricted

0 B

Comments

sa...@google.com <sa...@google.com> May 12, 2022 04:32AM

Assigned to ra...@google.com.

ra...@google.com <ra...@google.com> #2May 12, 2022 09:05AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

lk...@gmail.com <lk...@gmail.com> #3Jun 13, 2022 07:38AM

Any news on this? It is still a problem on Android 13 Beta 3.1.

di...@gmail.com <di...@gmail.com> #4Jun 17, 2022 10:25AM

I don't know. I quitted android 13 beta due to too much instability.

On Mon, 13 Jun 2022 at 08:39, <buganizer-system@google.com> wrote:

- Show quoted text -

ad...@google.com <ad...@google.com> #5Jul 11, 2022 08:08AM

Marked as fixed.

The issue has been fixed and it will be available in a future build.

ok...@gmail.com <ok...@gmail.com> #6Jul 14, 2022 08:17AM

The issue is still present in Beta 4. Is this fix included in Beta 4?

ok...@gmail.com <ok...@gmail.com> #7Jul 21, 2022 05:15AM

Pls update the status of the fix. The issue is still there in Beta 4 though it is marked fixed.

ro...@gmail.com <ro...@gmail.com> #8Aug 31, 2022 07:04PM

Do we have an update on this? I can still see this not working on Android 13 official release

me...@gmail.com <me...@gmail.com> #9Sep 15, 2022 01:15AM

seem here on Pixel 6 with Android 13 official build

su...@gmail.com <su...@gmail.com> #10Jul 21, 2023 06:28PM

Issue still exists, any update or resolution planned?
Samsung Galaxy S21 Ultra, Android 13 (OneUI 5.1)