> -----Original Message----- > From: Jan Mulder [mailto:jlmul...@xs4all.nl] > Sent: Tuesday, 18 July 2017 10:04 > To: Alex Blasche <alexander.blas...@qt.io>; Dirk Hohndel <d...@hohndel.org> > Cc: Subsurface Mailing List <subsurface@subsurface-divelog.org> > Subject: Re: OSTC over BLE experiences and questions > > On 14-07-17 08:34, Alex Blasche wrote: > > > >>> The immediate problem that I believe I can see is that the state > >>> machine has a missing end transition on my side. The last descriptor > >>> read of the service discovery is a failure and therefore the usual > >>> Android callbacks which finish the discovery do not kick in. I have > >>> to add an exit conditions which unfortunately means that you'll need > >>> a custom patch for QtBluetoothLE.java. I am stuck in workshop today and > tomorrow. I'll try to squeeze it somewhere in between. > > > > Ok, here is the patch: https://codereview.qt-project.org/#/c/200076/ > > > > I was not able to test this due to lack of being able to setup a test > > server that > has exactly this behavior. Hopefully you can verify for me that this finished > the > service discovery. If it is successful you should see the following logging > output: > > > > W QtBluetoothGatt: Finished current discovery for service handle <xyz> > > Ok, I compiled Qt 5.9.1 (using your configure spec) including the patch > (200079) above and tested the transfer. The finished current discovery message > is shown in the logcat. So, this patch LGTM.
Thank you very much for the feedback. Consider this patch part of 5.9.2 Please let me know if you run into more problems. > > In addition there is one more patch which you may need if you encounter > Dirk's problem with MTU handling: > > > > https://codereview.qt-project.org/#/c/199117/ > > Did not try this (yet). It does not seem related to my interface process. Probably not needed for your device. It seems to honour the default MTU value. -- Alex _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
