We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2018-05-09 17:08:50 +0200

BLE GATT/GAP Server in bluez5 not working as expected

While writing an app that does BLE GATT to a watch, i found that I get disconnected routinely every 15 minutes. I logged all the traffic from an android device, and found that every 120 seconds, the watch does the following command: Read By Type Request, Device Name, Handles: 0x0001..0xffff

On android, this returns the device name as expected. On sailfish, this returns 'Request not supported' as per the following btmon log:

ACL Data RX: Handle 6 flags 0x02 dlen 11 #1086 [hci0] 820.764748 ATT: Read By Type Request (0x08) len 6 Handle range: 0x0001-0xffff Attribute type: Device Name (0x2a00) < ACL Data TX: Handle 6 flags 0x00 dlen 9 #1087 [hci0] 820.765724 ATT: Error Response (0x01) len 4 Read By Type Request (0x08) Handle: 0x0000 Error: Request Not Supported (0x06)

Bluez devs believe this works fine upstream, and tested it, so put the blame on the mer build.

Are there any patches that would break this? Any config needed to enable this?

Next step for me is to write a quite desktop app and see what bluez on my deskop returns.

BLE GATT/GAP Server in bluez5 not working as expected

While writing an app that does BLE GATT to a watch, i found that I get disconnected routinely every 15 minutes. I logged all the traffic from an android device, and found that every 120 seconds, the watch does the following command: Read By Type Request, Device Name, Handles: 0x0001..0xffff

On android, this returns the device name as expected. On sailfish, this returns 'Request not supported' as per the following btmon log:

ACL Data RX: Handle 6 flags 0x02 dlen 11 #1086 [hci0] 820.764748 ATT: Read By Type Request (0x08) len 6 Handle range: 0x0001-0xffff Attribute type: Device Name (0x2a00) < ACL Data TX: Handle 6 flags 0x00 dlen 9 #1087 [hci0] 820.765724 ATT: Error Response (0x01) len 4 Read By Type Request (0x08) Handle: 0x0000 Error: Request Not Supported (0x06)

Bluez devs believe this works fine upstream, and tested it, so put the blame on the mer build.

Are there any patches that would break this? Any config needed to enable this?

Next step for me is to write a quite desktop app and see what bluez on my deskop returns.

BLE GATT/GAP Server in bluez5 not working as expected

While writing an app that does BLE GATT to a watch, i found that I get disconnected routinely every 15 minutes. I logged all the traffic from an android device, and found that every 120 seconds, the watch does the following command: Read By Type Request, Device Name, Handles: 0x0001..0xffff

On android, this returns the device name as expected. On sailfish, this returns 'Request not supported' as per the following btmon log:

ACL Data RX: Handle 6 flags 0x02 dlen 11 #1086 [hci0] 820.764748 ATT: Read By Type Request (0x08) len 6 Handle range: 0x0001-0xffff Attribute type: Device Name (0x2a00) < ACL Data TX: Handle 6 flags 0x00 dlen 9 #1087 [hci0] 820.765724 ATT: Error Response (0x01) len 4 Read By Type Request (0x08) Handle: 0x0000 Error: Request Not Supported (0x06)

Bluez devs believe this works fine upstream, and tested it, so put the blame on the mer build.

Are there any patches that would break this? Any config needed to enable this?

Next step for me is to write a quite desktop app and see what bluez on my deskop returns.