Re: [TEST REQUEST] Windows Bluetooth LE build
On Mon, 1 Oct 2018 at 16:17, Dirk Hohndel wrote: > > > > On Sep 30, 2018, at 6:40 PM, Lubomir I. Ivanov wrote: > >> > >> Rebooted. Nothing else running, just the cmd.exe > >> > >> Same output - semaphore timeout period has expired. > >> > > did some more testing here. my phone's BT is off all the time, i don't anything to use it with. i'm able to reproduce this error if i pair and connect my phone using NRF Connect with the DC, and then try to connect and write a descriptor using the qt-bt-discovery.exe app. to get out of this scenario i disconnect from the NRF Connect app. at this point qt-bt-discovery.exe writes the descriptor correctly. but this is not consistent - it can lead into all sorts of weird conditions, like: - writing the descriptor from the .EXE app disconnects the phone. - if the phone is disconnected after that, it can no longer connect to the device and the phone BT has to be turned off/on. - if the phone "takes ownership" of the device, the Windows BT has to be turned off/on, but then it decides to forget the the DC 50% of the time. - rediscovering the device in Windows might fail to pair or the discovery process even crashes - OS restart is required. this proves to me that there are ownership issues here, but also that the whole process is quite unreliable. so if another device other than the Windows laptop is connected to the DC, writing to a service will simply fail with the semaphore error and there would be no other indication. could you try turning all suspect local devices off for such a test? ...but something else here, the Qt code is doing everything correctly and i cannot blame it, at this point. for now i can only blame Windows' BT support and BT as a whole. > Also, how do I quit the program? Ctrl-C doesn't appear to work. All I can > figure out is kill the cmd.exe. > That doesn't seem like the right way to do this :-) > i have updated the test app to now properly exit on ctrl+c: https://www.dropbox.com/s/ehkoklydtnrvzxg/_qt-bt-discovery.zip?dl=0 lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: which additional MXE packages do you need installed?
Hi Dirk. On Mon, Oct 01, 2018 at 05:59:29AM -0700, Dirk Hohndel wrote: > Hi Salvador, > > Right now our Travis build is downloading a second MXE install for you - the > comment in the before_install.sh indicates mdbtools and glib... is that all? Yes that's all ... but ... mdbtools builds static so glib-2.0 must be built both shared and static. BTW, the paths in my tarball are different from yours. Although binaries get merged in their correct paths in the travis VM; if you are thinking about include them in your tarball, this may need some changes in scripts/windows/before_install.sh > Also, you clone mdbtools there, and then try to build those instead of the > ones download with MXE... but then are falling back to MXE if the build > fails... that all seems a little odd - am I missing something? > The idea is to use the latest avaliable mdbtools, assuming it can include some recent fix and distros or mxe may be slow at including them in their sources. The reality is that mdbtools' last commit is from January 2017 so we can drop this step, if you want and, and simply use the mxe binaries. > The reason I'm asking is that I'm trying to update Travis to a newer MXE > version, and I'm afraid things will clash with the binaries that you then > install on top... > Almost sure they will. I'm building at this moment mxe binaries from 97c0fbf in my "notsopowerful" laptop and will send a PR as soon I've tested them to work. Best regards. Salva. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [TEST REQUEST] Windows Bluetooth LE build
On Mon, 1 Oct 2018 at 16:17, Dirk Hohndel wrote: > > > > On Sep 30, 2018, at 6:40 PM, Lubomir I. Ivanov wrote: > >> > >> Rebooted. Nothing else running, just the cmd.exe > >> > >> Same output - semaphore timeout period has expired. > >> > > > > side questions: > > - does random addresses set to off make a difference? > > No, I seem to get the same results. > > > - is that the correct descriptor to enable notifications? > > > > Yes. > > Also, how do I quit the program? Ctrl-C doesn't appear to work. All I can > figure out is kill the cmd.exe. > That doesn't seem like the right way to do this :-) > sorry, i seem to be out of ideas at this point. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [TEST REQUEST] Windows Bluetooth LE build
On Mon, 1 Oct 2018 at 16:17, Dirk Hohndel wrote: > > > > On Sep 30, 2018, at 6:40 PM, Lubomir I. Ivanov wrote: > >> > >> Rebooted. Nothing else running, just the cmd.exe > >> > >> Same output - semaphore timeout period has expired. > >> > > > > side questions: > > - does random addresses set to off make a difference? > > No, I seem to get the same results. > > > - is that the correct descriptor to enable notifications? > > > > Yes. > > Also, how do I quit the program? Ctrl-C doesn't appear to work. All I can > figure out is kill the cmd.exe. > That doesn't seem like the right way to do this :-) > was too tired to add proper handling of the second thread. can be started from explorer too and closed with the [x]. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [TEST REQUEST] Windows Bluetooth LE build
> On Sep 30, 2018, at 6:40 PM, Lubomir I. Ivanov wrote: >> >> Rebooted. Nothing else running, just the cmd.exe >> >> Same output - semaphore timeout period has expired. >> > > side questions: > - does random addresses set to off make a difference? No, I seem to get the same results. > - is that the correct descriptor to enable notifications? > Yes. Also, how do I quit the program? Ctrl-C doesn't appear to work. All I can figure out is kill the cmd.exe. That doesn't seem like the right way to do this :-) /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
