Fixed

Bug

Status Update

No update yet.

Description

da...@gmail.com

created issue #1

Sep 7, 2022 01:13PM

Summary:

We have the headset and mobile app which communicates with it. Communication between the headset and the mobile device using BLE is performed using the GATT profile. The problems occur when the app starts to attempt the encrypted write characteristic, the pairing request appears at every write characteristic after every GATT disconnection and connection.

Steps to reproduce:

Get our Bluetooth device from BluetoothAdapter.bondedDevices and filter by the MAC address of the bonded peripheral.
connectGatt to the filtered device
discoverServices
enableNotifications for read characteristic
Send write characteristic which initiate a security request from Android to the peripheral firmware, which in turn triggers a Bluetooth pairing (bonding) dialog to appear to the user.
Approve pairing request, which results in the characteristic write succeeding
disconnect GATT
connect GATT again to the same device
repeat all the steps from 3-5.
Observe that the pairing request appears again, but there should be no pairing request, as it was approved in step №5

Investigation notes

The issue occurs with all Android 13 versions (with security patches from 05.08.2022 and 05.09.2022)
The rebooting of the phone helps to resolve that issue, after rebooting the write characteristic works well, without triggering a Bluetooth pairing (bonding) dialog to appear again to the user.

Logs:

2022-09-07 15:35:31.137 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: connect() - device: 00:0A:9B:97:B4:EF, auto: false
2022-09-07 15:35:31.138 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: registerApp()
2022-09-07 15:35:31.138 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: registerApp() - UUID=d231b99d-41cb-4f12-b8d3-a0cec5fc1e43
2022-09-07 15:35:31.141 12319-12333/com.mmalai.ble_tests D/BluetoothGatt: onClientRegistered() - status=0 clientIf=7
2022-09-07 15:35:31.302 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=7 device=00:0A:9B:97:B4:EF
2022-09-07 15:35:31.302 12319-13224/com.mmalai.ble_tests W/BluetoothGattCallback: Successfully connected to 00:0A:9B:97:B4:EF
2022-09-07 15:35:31.302 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: discoverServices() - device: 00:0A:9B:97:B4:EF
2022-09-07 15:35:31.491 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onConnectionUpdated() - Device=00:0A:9B:97:B4:EF interval=24 latency=0 timeout=500 status=59
2022-09-07 15:35:32.224 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onConnectionUpdated() - Device=00:0A:9B:97:B4:EF interval=72 latency=4 timeout=400 status=0
2022-09-07 15:35:34.661 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onSearchComplete() = Device=00:0A:9B:97:B4:EF Status=0
2022-09-07 15:35:34.702 12319-13224/com.mmalai.ble_tests I/printGattTable: Service 00001801-0000-1000-8000-00805f9b34fb
    Characteristics:
    |--00002a05-0000-1000-8000-00805f9b34fb	->	00002902-0000-1000-8000-00805f9b34fb
    |--00002b29-0000-1000-8000-00805f9b34fb	->	
    Service 00001800-0000-1000-8000-00805f9b34fb
    Characteristics:
    |--00002a00-0000-1000-8000-00805f9b34fb	->	
    |--00002a01-0000-1000-8000-00805f9b34fb	->	
    Service cd007f80-8b0b-11e6-ae22-56b6b6499611
    Characteristics:
    |--cd007f82-8b0b-11e6-ae22-56b6b6499611	->	00002902-0000-1000-8000-00805f9b34fb
    |--cd007f81-8b0b-11e6-ae22-56b6b6499611	->	
    Service 00001100-d102-11e1-9b23-00025b00a5a5
    Characteristics:
    |--00001101-d102-11e1-9b23-00025b00a5a5	->	
    |--00001102-d102-11e1-9b23-00025b00a5a5	->	00002902-0000-1000-8000-00805f9b34fb
    |--00001103-d102-11e1-9b23-00025b00a5a5	->	00002902-0000-1000-8000-00805f9b34fb
2022-09-07 15:35:34.703 12319-13224/com.mmalai.ble_tests D/BluetoothGattCallback: notify: true, indicate: true, write: false
2022-09-07 15:35:34.704 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: setCharacteristicNotification() - uuid: cd007f82-8b0b-11e6-ae22-56b6b6499611 enable: true
2022-09-07 15:35:35.196 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onConnectionUpdated() - Device=00:0A:9B:97:B4:EF interval=72 latency=4 timeout=400 status=59
2022-09-07 15:35:35.196 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: setCharacteristicNotification() - uuid: cd007f82-8b0b-11e6-ae22-56b6b6499611 enable: true
2022-09-07 15:35:35.202 12319-13224/com.mmalai.ble_tests D/BluetoothGattCallback: Write completed for descriptor 00002902-0000-1000-8000-00805f9b34fb, status: 0!
2022-09-07 15:35:38.608 12319-12319/com.mmalai.ble_tests D/MainActivity: notify: false, indicate: false, write: true, write no response: false
2022-09-07 15:35:41.261 12319-12319/com.mmalai.ble_tests D/MainActivity: bondReceiver, got BOND_BONDING
2022-09-07 15:35:41.284 12319-12319/com.mmalai.ble_tests E/MainActivity: action android.bluetooth.device.action.PAIRING_REQUEST
2022-09-07 15:35:46.487 12319-13224/com.mmalai.ble_tests D/BluetoothGattCallback: Received data from notification of cd007f82-8b0b-11e6-ae22-56b6b6499611: [0x40, 0x0, 0x0]
2022-09-07 15:35:46.487 12319-13224/com.mmalai.ble_tests I/BluetoothGattCallback: Wrote to characteristic cd007f81-8b0b-11e6-ae22-56b6b6499611 | value: [0x3, 0x0, 0x0]
2022-09-07 15:35:48.345 12319-12319/com.mmalai.ble_tests D/MainActivity: bondReceiver, got BOND_BONDED, going to connect GATT
2022-09-07 15:36:50.184 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: cancelOpen() - device: 00:0A:9B:97:B4:EF
2022-09-07 15:36:50.194 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=7 device=00:0A:9B:97:B4:EF
2022-09-07 15:36:50.194 12319-13224/com.mmalai.ble_tests W/BluetoothGattCallback: Successfully disconnected from 00:0A:9B:97:B4:EF
2022-09-07 15:36:50.194 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: close()
2022-09-07 15:36:50.194 12319-13224/com.mmalai.ble_tests D/BluetoothGatt: unregisterApp() - mClientIf=7
2022-09-07 15:36:55.050 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: connect() - device: 00:0A:9B:97:B4:EF, auto: false
2022-09-07 15:36:55.050 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: registerApp()
2022-09-07 15:36:55.050 12319-12319/com.mmalai.ble_tests D/BluetoothGatt: registerApp() - UUID=bcbf2989-3e79-4fbb-9a4a-5d3d4b4d4872
2022-09-07 15:36:55.052 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: onClientRegistered() - status=0 clientIf=7
2022-09-07 15:36:55.107 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=7 device=00:0A:9B:97:B4:EF
2022-09-07 15:36:55.107 12319-12334/com.mmalai.ble_tests W/BluetoothGattCallback: Successfully connected to 00:0A:9B:97:B4:EF
2022-09-07 15:36:55.107 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: discoverServices() - device: 00:0A:9B:97:B4:EF
2022-09-07 15:36:55.112 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: onSearchComplete() = Device=00:0A:9B:97:B4:EF Status=0
2022-09-07 15:36:55.113 12319-12334/com.mmalai.ble_tests I/printGattTable: Service 00001801-0000-1000-8000-00805f9b34fb
    Characteristics:
    |--00002a05-0000-1000-8000-00805f9b34fb	->	00002902-0000-1000-8000-00805f9b34fb
    |--00002b29-0000-1000-8000-00805f9b34fb	->	
    Service 00001800-0000-1000-8000-00805f9b34fb
    Characteristics:
    |--00002a00-0000-1000-8000-00805f9b34fb	->	
    |--00002a01-0000-1000-8000-00805f9b34fb	->	
    Service cd007f80-8b0b-11e6-ae22-56b6b6499611
    Characteristics:
    |--cd007f82-8b0b-11e6-ae22-56b6b6499611	->	00002902-0000-1000-8000-00805f9b34fb
    |--cd007f81-8b0b-11e6-ae22-56b6b6499611	->	
    Service 00001100-d102-11e1-9b23-00025b00a5a5
    Characteristics:
    |--00001101-d102-11e1-9b23-00025b00a5a5	->	
    |--00001102-d102-11e1-9b23-00025b00a5a5	->	00002902-0000-1000-8000-00805f9b34fb
    |--00001103-d102-11e1-9b23-00025b00a5a5	->	00002902-0000-1000-8000-00805f9b34fb
2022-09-07 15:36:55.113 12319-12334/com.mmalai.ble_tests D/BluetoothGattCallback: notify: true, indicate: true, write: false
2022-09-07 15:36:55.114 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: setCharacteristicNotification() - uuid: cd007f82-8b0b-11e6-ae22-56b6b6499611 enable: true
2022-09-07 15:36:55.198 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: setCharacteristicNotification() - uuid: cd007f82-8b0b-11e6-ae22-56b6b6499611 enable: true
2022-09-07 15:36:55.201 12319-12334/com.mmalai.ble_tests D/BluetoothGattCallback: Write completed for descriptor 00002902-0000-1000-8000-00805f9b34fb, status: 0!
2022-09-07 15:36:56.053 12319-12334/com.mmalai.ble_tests D/BluetoothGatt: onConnectionUpdated() - Device=00:0A:9B:97:B4:EF interval=72 latency=4 timeout=400 status=0
2022-09-07 15:37:00.438 12319-12319/com.mmalai.ble_tests D/MainActivity: notify: false, indicate: false, write: true, write no response: false
2022-09-07 15:37:10.347 12319-12319/com.mmalai.ble_tests D/MainActivity: notify: false, indicate: false, write: true, write no response: false
2022-09-07 15:37:12.302 12319-12319/com.mmalai.ble_tests D/MainActivity: bondReceiver, got BOND_BONDING
2022-09-07 15:37:12.313 12319-12319/com.mmalai.ble_tests E/MainActivity: action android.bluetooth.device.action.PAIRING_REQUEST
2022-09-07 15:37:19.821 12319-12319/com.mmalai.ble_tests D/MainActivity: bondReceiver, got BOND_BONDED, going to connect GATT
2022-09-07 15:37:30.720 12319-12319/com.mmalai.ble_tests D/MainActivity: notify: false, indicate: false, write: true, write no response: false
2022-09-07 15:37:31.602 12319-12335/com.mmalai.ble_tests D/BluetoothGattCallback: Received data from notification of cd007f82-8b0b-11e6-ae22-56b6b6499611: [0x40, 0x0, 0x0]
2022-09-07 15:37:31.602 12319-12335/com.mmalai.ble_tests I/BluetoothGattCallback: Wrote to characteristic cd007f81-8b0b-11e6-ae22-56b6b6499611 | value: [0x3, 0x0, 0x0]

Also attaching the video from the test app with the same flow as in the logs

video_2022-09-07_16-11-48.mp4

3.5 MB

Download

Comments

be...@gmail.com <be...@gmail.com> #2Sep 7, 2022 07:47PM

After September security update problem still persists to connect to android auto with pixel 6.

vi...@google.com <vi...@google.com> #3Sep 8, 2022 05:12AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build Which Android build are you using? (e.g. OPP1.170223.012)

Device used Which device did you use to reproduce this issue?

Issue details Please explain the issue in detail.

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

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

Related API or developer doc (*Required)

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue) For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

da...@gmail.com <da...@gmail.com> #4Sep 8, 2022 09:48AM

Android build Which Android build are you using? Pixel 5 13(TP1A.220624.014), Pixel 4Xl 13(TP1A.220905.004), Pixel 6 13 (TP1A.220905.004),

Unfortunately, we are using the external hardware device with which our app is communicating, and I'm not sure that the sample apk or any docs will help you without the actual device. But in general, the issue is what I describe in description:

We send the encrypted write characteristic to device, and device responds with the GATT_INSUFFICIENT_AUTHENTICATION(0x05), which triggers bonding process at the every GATT connection, even if the bonding was accepted at the previous connection. To resolve that issue you need to reboot the phone, and after that encrypted write characteristic passing succesufully.

Providing you the HCI Bluetooth logs in Google docs.Hope it will help you.

https://drive.google.com/file/d/1F28mTcAiimCQq9o-cpTee8dS1Jl-wT0N/view?usp=drive_web (bugreport-redfin-TP1A.220624.014-2022-09-08-12-30-59.zip)

da...@gmail.com <da...@gmail.com> #5Sep 8, 2022 10:55AM

Also sharing with you a test app, where we are able to reproduce that issue. Thanks in advance.

https://drive.google.com/file/d/18pMDHYEXRVnA499xbWknEcVDTcRZoVr8/view?usp=drive_web (ble-tests.zip)

da...@gmail.com <da...@gmail.com> #6Sep 12, 2022 11:07AM

Do you need any additional info from my side?

vi...@google.com <vi...@google.com> #7Sep 12, 2022 11:38AM

Thanks for the information, we’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

da...@gmail.com <da...@gmail.com> #8Oct 3, 2022 09:53AM

Hi, any updates on that issue?

my...@gmail.com <my...@gmail.com> #9Apr 10, 2023 06:56PM

Could you connect to the device without pairing to get around the dialog?

vi...@google.com <vi...@google.com> #10May 21, 2023 01:08PM

Marked as fixed.

The development team has fixed the issue and it will be available in a future build.

IssueTracker

Android 13: The system requires BLE approving request at every GATT connection

Status Update

Description

Summary:

Steps to reproduce:

Investigation notes

Logs:

Comments

be...@gmail.com <be...@gmail.com> #2Sep 7, 2022 07:47PM

vi...@google.com <vi...@google.com> #3Sep 8, 2022 05:12AM

da...@gmail.com <da...@gmail.com> #4Sep 8, 2022 09:48AM

da...@gmail.com <da...@gmail.com> #5Sep 8, 2022 10:55AM

da...@gmail.com <da...@gmail.com> #6Sep 12, 2022 11:07AM

vi...@google.com <vi...@google.com> #7Sep 12, 2022 11:38AM

da...@gmail.com <da...@gmail.com> #8Oct 3, 2022 09:53AM

my...@gmail.com <my...@gmail.com> #9Apr 10, 2023 06:56PM

vi...@google.com <vi...@google.com> #10May 21, 2023 01:08PM

Issue 245501768

Description

Summary:

Steps to reproduce:

Investigation notes

Logs:

Issue summary

Comments

be...@gmail.com <be...@gmail.com> #2Sep 7, 2022 07:47PM

vi...@google.com <vi...@google.com> #3Sep 8, 2022 05:12AM

da...@gmail.com <da...@gmail.com> #4Sep 8, 2022 09:48AM

da...@gmail.com <da...@gmail.com> #5Sep 8, 2022 10:55AM

da...@gmail.com <da...@gmail.com> #6Sep 12, 2022 11:07AM

vi...@google.com <vi...@google.com> #7Sep 12, 2022 11:38AM

da...@gmail.com <da...@gmail.com> #8Oct 3, 2022 09:53AM

my...@gmail.com <my...@gmail.com> #9Apr 10, 2023 06:56PM

vi...@google.com <vi...@google.com> #10May 21, 2023 01:08PM

Add comment

Issue metadata