search icon
Close

What are you looking for?

cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 

Bluetooth LE device connection stability problems with Samsung S20 FE running Android 13

(Topic created on: 09-02-2024 10:21 AM)
2549 Views
Members_dCux8IO
First Poster

‎09-02-2024 10:21 AM - last edited ‎09-02-2024 12:30 PM

Options

Dear Samsung Community and support experts,

I'm experiencing severe connection stability problems with my Samsung S20 FE running Android 13 when trying to connect to Bluetooth Low Energy (BLE) devices. I have experienced that at least with 2 different BLE devices already and tried to debug it by myself.

But unfortunately I'm lacking sufficient knowledge about the Bluetooth LE connection procedure in order to be able to understand the Bluetooth HCI Snoop logs that I have captured after reproducing the problem.

I'm therefore posting them here, hoping that there are other experts from the Samsung Community reading this and able to help.

I have linked below the mentioned Bluetooth Snoop HCI logs, which was already decoded in text format: 

btsnoop_hci_202402061828.txt

The only thing that I have been able to read from the logs is that it seems that a Connection Timeout occurs and connection is retried in a endless loop.

No.  Time            Source     Destination Protocol Length Info 
1601 19:27:10.200830 controller host        HCI_EVT  34     Rcvd LE Meta (LE Enhanced Connection Complete)

Frame 1601: 34 bytes on wire (272 bits), 34 bytes captured (272 bits)
Encapsulation type: Bluetooth H4 with linux header (99)
Arrival Time: Feb 6, 2024 19:27:10.200830000 W. Europe Standard Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1707244030.200830000 seconds
[Time delta from previous captured frame: 0.003597000 seconds]
[Time delta from previous displayed frame: 0.003597000 seconds]
[Time since reference or first frame: 935.058482000 seconds]
Frame Number: 1601
Frame Length: 34 bytes (272 bits)
Capture Length: 34 bytes (272 bits)
[Frame is marked: False]
[Frame is ignored: False]
Point-to-Point Direction: Received (1)
[Protocols in frame: bluetooth:hci_h4:bthci_evt]
Bluetooth
[Source: controller]
[Destination: host]
Bluetooth HCI H4
[Direction: Rcvd (0x01)]
HCI Packet Type: HCI Event (0x04)
Bluetooth HCI Event - LE Meta
Event Code: LE Meta (0x3e)
Parameter Total Length: 31
Sub Event: LE Enhanced Connection Complete (0x0a)
Status: Success (0x00)
Connection Handle: 0x0002
Role: Currently the Master for specified BD_ADDR (0x00)
**bleep** Address Type: Public Device Address (0x00)
BD_ADDR: Thinking_5f:eb:88 (44:a6:e5:5f:eb:88)
Local Resolvable Private Address: 00:00:00_00:00:00 (00:00:00:00:00:00)
**bleep** Resolvable Private Address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Connection Interval: 36 (45 msec)
Connection Latency: 0 (number events)
Supervision Timeout: 500 (5 sec)
Master Clock Accuracy: 251-500 ppm (0x00)

[Frame 1602 ... Frame 1719]

No.  Time            Source     Destination Protocol Length Info 
1720 19:27:16.347789 controller host        HCI_EVT  7      Rcvd Disconnect Complete

Frame 1720: 7 bytes on wire (56 bits), 7 bytes captured (56 bits)
Encapsulation type: Bluetooth H4 with linux header (99)
Arrival Time: Feb 6, 2024 19:27:16.347789000 W. Europe Standard Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1707244036.347789000 seconds
[Time delta from previous captured frame: 1.413332000 seconds]
[Time delta from previous displayed frame: 1.413332000 seconds]
[Time since reference or first frame: 941.205441000 seconds]
Frame Number: 1720
Frame Length: 7 bytes (56 bits)
Capture Length: 7 bytes (56 bits)
[Frame is marked: False]
[Frame is ignored: False]
Point-to-Point Direction: Received (1)
[Protocols in frame: bluetooth:hci_h4:bthci_evt]
Bluetooth
[Source: controller]
[Destination: host]
Bluetooth HCI H4
[Direction: Rcvd (0x01)]
HCI Packet Type: HCI Event (0x04)
Bluetooth HCI Event - Disconnect Complete
Event Code: Disconnect Complete (0x05)
Parameter Total Length: 4
Status: Success (0x00)
Connection Handle: 0x0002
Reason: Connection Timeout (0x08)



Now the question is why the timeout occurs. I also see a few negative acknowledgements "Rcvd Error Response - Attribute Not Found" from the Bluetooth Low Energy (BLE) device during the connection procedure, but I'm not sure if these could be related to root cause of the problem or not:

No.  Time            Source                          Destination                           Protocol Length Info 
1636 19:27:10.532763 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x0001 (Generic Access Profile)
1646 19:27:10.802832 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x000b (Generic Access Profile: Peripheral Preferred Connection Parameters)
1650 19:27:10.832750 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x000c (Device Information)
1662 19:27:10.945111 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x001e (Device Information: PnP ID)
1666 19:27:10.967642 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x001f (Service Discovery Server Service Class ID)
1675 19:27:11.057788 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x002e (Service Discovery Server Service Class ID: Unknown)
1694 19:27:11.192715 Thinking_5f:eb:88 (ABT-2IG1259) SamsungE_ef:bb:52 (S20 FE von XXXXXX) ATT      14     Rcvd Error Response - Attribute Not Found, Handle: 0x0030 (Service Discovery Server Service Class ID: Unknown: Unknown)

The Bluetooth BLE device that I tried to connect to in this example log is a material moisture measuring device "Dampmaster Compact Pro" from the German company "UMAREX GmbH & Co.KG" and "Laserliner" is one of their brand names
See https://www.laserliner.com/en/products/4021563696468-dampmaster-compact-pro.html for further details.

This BLE device needs to be connected from Android via using this this app called "Laserliner MeasureNote"
https://play.google.com/store/apps/details?id=com.soft4.Laserliner.MeasureNote&hl=en_US

As the device uses following Bluetooth MAC-Address:

BD_ADDR: Thinking_5f:eb:88 (44:a6:e5:5f:eb:88)

I have looked up that the bluetooth interface from that device seems to be from Chinese manufacturer "THINKING TECHNOLOGY CO.,LTD"
See https://www.tuner168.com/ or https://ttcble.com/ for their English website.

I should mention that I have also tried to connect the same BLE device to my Samsung S6 Lite Tablet running Android 14, and with that Android device, the connection to the same BLE device seems to work reliably and stable.

I would be really happy if someone from the Community could support here. I'm looking forward to hearing from you.

Many thanks in advance for looking at this.

0 Likes
0 REPLIES 0