Hi Sven, On Mon, Mar 7, 2016 at 7:50 PM, Sven Harmstorf <sven.harmstorf@xxxxxxxxxxxxx> wrote: > Hello, > > I am running BlueZ 5.37 on Linux kernel 4.1.6 with an Atheros AR3012 adapter configured to advertise a service using the experimental D-Bus GATT API on a Freescale i.MX6 Quad (ARMv7l). > > The advertising is working fine (verified this via Nordic’s Android App 'nRF Master Control Panel‘). > Connecting and discovering services/characteristics is also working without any issues. > > One of the characteristics has the property "flags" set to ["write-without-response“, "notify“]. > Centrals should write their data quickly without the need to wait for a response (accepting the potential data loss) and get value changes only via notification. Explicit read is not supported. > > When a central sends multiple writes of 1-20 bytes in a row, only the first write succeeds. Any following writes fail in src/shared/gatt-server.c:786. As a result of this, only a few writes happen to be sent as a signal on the D-Bus. Actually there is a simple fix for this which is to use no reply messages, it perhaps was the intention given the lack of queuing of bt_gatt_server, for regular write this should never happen. -- 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
