Bluetooth LE BluetoothDevice.connectGatt fails over time to any peripheral in any app [125138967]

Obsolete

Bug

[AOSP] assigned

Status Update

No update yet.

Description

zs...@gmail.com

created issue #1

Feb 21, 2019 02:50PM

Multiple cycles of simultaneous GATT connects and disconnects to multiple nearby peripherals make the app fail to connect, after a while. This affects all apps (i.e., it has nothing to do with the app). Once the device is in this state, no app can connect to any Bluetooth LE peripheral.

I wrote a small app based on the BluetoothLeGatt Google sample code that demonstrates this issue. The demo app scans for nearby Bluetooth LE peripherals and shows them in a list while connecting to them. After a connection to a peripheral is made, it removes the peripheral from the list and starts the cycle over.

Android build
7.0 NRD90M.G925TUVS6FRC1
7.1.1 NMF26X.J510FNXXU2BRE6

Steps to reproduce
1. Download and run the demo app:

https://github.com/zssz/BluetoothLeGatt
2. Upon first run allow access to the device's coarse location for scanning for peripherals to work. Restart scanning in the top right corner.
3. Make sure there are Bluetooth LE peripherals in range. Note: the more, the better, because the issue will appear sooner. In my case with 7 peripherals the issue appears under 3 minutes.
4. Leave the app running.

Expected result
Until the app is stopped, you can see peripherals appearing in the list and shortly after disappearing.

Actual result
After a while, depending on the number of nearby peripherals, you can see that the list doesn't change anymore. This means that all of the peripherals are in the connecting state, but won't connect.

Frequency
100%

Video recording

https://youtu.be/AnbkHN7suPE

Fix
Restarting the app doesn't fix the issue. Neither toggling Bluetooth in Settings. I found 3 ways of fixing it — all of them require user intervention, unfortunately:
a) Go to Settings / Apps / ... / Show system apps / Bluetooth / Storage / CLEAR DATA
b) Go to Settings / Apps / ... / Show system apps / Bluetooth / FORCE STOP
c) Reboot the device

Comments

ad...@google.com <ad...@google.com> #2Feb 22, 2019 12:01PM

Assigned to ad...@google.com.

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

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

Can you confirm if this issue is reproducible on Pixel/Nexus device (on latest O or P builds) ?

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.

zs...@gmail.com <zs...@gmail.com> #3Feb 22, 2019 01:22PM

Device used
Samsung Galaxy S6 Edge SM-G925T
Samsung Galaxy J5 (2016) SM-J510FN

I can not confirm this issue is reproducible on Pixel/Nexus device (on latest O or P builds) because I don't have access to those devices, unfortunately.

Android bug report

https://drive.google.com/open?id=1JInkabGTD0BVRFCBweBWZ479BRnf0Dgz

ad...@google.com <ad...@google.com> #4Feb 25, 2019 11:37AM

The bug report shared in

comment #3

seems to be corrupted. Please capture & share a new bug report.

zs...@gmail.com <zs...@gmail.com> #5Feb 25, 2019 11:45AM

I uploaded it again and double checked that it can be downloaded and opened:

https://drive.google.com/open?id=1ype-0Oh6VlZ6TY20YRkTQrH_5-uP4_4P

ad...@google.com <ad...@google.com> #6Feb 25, 2019 12:40PM

We have passed this to the development team and will update this issue with more information as it becomes available.

ad...@google.com <ad...@google.com> #7May 31, 2020 10:14AM

Status: Won't Fix (Obsolete)

We limit number of GATT clients available in the system. If any app leaks the connections, it might cause such issue.

To find which app is misbehaving, you can do this in real time:
adb shell dumpsys bluetooth_manager | grep "GATT" -A20

[Deleted User] <[Deleted User]> #8Nov 25, 2022 09:59AM

Is it possible to forcibly close all GATT clients so that the application can connect?