Hi François, On Wed, Mar 2, 2016 at 9:31 AM, François Beaufort <beaufort.francois@xxxxxxxxx> wrote: > When writing to a characteristic and that a disconnection happens > before getting a write (error) response, BlueZ should inform that > write operation failed. > See my real example logs below: > > [DFU_Test:/service000c/char000d]# write 01 04 > Attempting to write /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000d > > > > < ACL Data TX: Handle 32 flags 0x00 dlen 9 > [hci0] 5.066808 > ATT: Write Request (0x12) len 4 > Handle: 0x000e > Data: 0104 >> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 5.106370 > Num handles: 1 > Handle: 32 > Count: 1 >> HCI Event: Vendor (0xff) plen 7 [hci0] 5.579396 > 82 12 95 40 10 36 59 ...@.6Y >> HCI Event: Disconnect Complete (0x05) plen 4 [hci0] 5.580376 > Status: Success (0x00) > Handle: 32 > Reason: Connection Timeout (0x08) > @ Device Disconnected: F1:6F:DE:EC:F1:D6 (2) reason 1 Interesting, does bluetoothctl print anything after this? -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
