Hi Luiz, On Sun, Jan 13, 2013 at 9:12 PM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > Hi Syam, > > On Fri, Jan 11, 2013 at 10:32 AM, Syam Sidhardhan <s.syam@xxxxxxxxxxx> wrote: >> Hi, >> >> We are using the obexd 0.48 version and testing the obexd. >> During testing OPP file send, we found one interoperability >> issue with the Windows7 PC stack and some commercialized devices >> available in the market. >> >> The issue is: OBEXD file transfer is getting failed >> once after the complete file content got transfferd. This is >> because of, we do a direct RFCOMM disconection rather than >> doing a proper OBEX disconection before. >> >> Does someone can help me a with a fix for this? > > We probably need to send a disconnect command before disconnecting > RFCOMM, iirc there was someone else looking into a similar problem > with a Nokia phone, the strange part is that the remote stack has > acknowledged the transfer complete and in theory we could go ahead and > start another one using the same session. > Yes, you are correct. We need to send a OBEX disconnect command before the RFCOMM disconnection. We have tried with the same and its working fine. Regards, Syam -- 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
