And I've just tried with latest trunk and it works perfectly! Thank you Luiz! [DFU_Test:/service000c/char000d]# write 01 04 Attempting to write /org/bluez/hci0/dev_F1_6F_DE_EC_F1_D6/service000c/char000d [CHG] Device F1:6F:DE:EC:F1:D6 Connected: no Failed to write: org.bluez.Error.Failed On Wed, Mar 9, 2016 at 1:17 PM, François Beaufort <beaufort.francois@xxxxxxxxx> wrote: > Thank you so much Luiz, > I'm going to test this tomorrow. > > In the mean time, which patches should be applied now if we want to > fix this in Chrome OS BlueZ? > > On Wed, Mar 9, 2016 at 11:53 AM, Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx> wrote: >> Hi François, >> >> On Mon, Mar 7, 2016 at 5:54 PM, Luiz Augusto von Dentz >> <luiz.dentz@xxxxxxxxx> wrote: >>> Hi François, >>> >>> On Mon, Mar 7, 2016 at 5:36 PM, François Beaufort >>> <beaufort.francois@xxxxxxxxx> wrote: >>>> (gentle ping) >>>> >>>> On Thu, Mar 3, 2016 at 10:46 AM, François Beaufort >>>> <beaufort.francois@xxxxxxxxx> wrote: >>>>> Since I'm expecting a response and device gets disconnected, I should >>>>> get a write error don't you think? >>> >>> Yes, it should probably return and error so the client is not left >>> hanging. I will investigate how this can be fixed. >> >> This should be fixed upstream, it will be part of 5.38 which should be >> coming out soon. >> >> -- >> 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
