Skip to content

Sometimes onServiceDiscoverd is not called when connecting. #536

Open
@cos-overclock

Description

@cos-overclock

The BleManager was used to connect with the peripheral device.
It is recognised that if the device is not a bonding device when connected, the discoverService is executed after a delay of 300 ms, but in reality the BluetoothGatt executes the discoverService immediately.
I don't know if this is the direct cause, but sometimes BleManager's onServicesDiscovered is not called.
Am I missing some setting that is required for the connection?

2023-11-13 16:48:17.882 31278-31432 BluetoothGatt                 D  connect() - device: 00:3C:84:13:9B:D5, auto: false
2023-11-13 16:48:17.882 31278-31432 BluetoothGatt                 D  registerApp()
2023-11-13 16:48:17.882 31278-31432 BluetoothGatt                 D  registerApp() - UUID=3c4f615a-b9f9-4bbc-bf0e-f566a7b50f0d
2023-11-13 16:48:17.886 31278-31348 BluetoothGatt                 D  onClientRegistered() - status=0 clientIf=6
2023-11-13 16:48:18.187 31278-31291 BluetoothGatt                 D  onClientConnectionState() - status=0 clientIf=6 device=00:3C:84:13:9B:D5
2023-11-13 16:48:18.187 31278-31278 MyBleManager                  I  Connected to 00:3C:84:13:9B:D5
2023-11-13 16:48:18.189 31278-31278 BleConnect...onObserver       D  ConnectionObserver.onDeviceConnected
2023-11-13 16:48:18.491 31278-31278 BluetoothGatt                 D  discoverServices() - device: 00:3C:84:13:9B:D5

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions