<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-GB link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>4.9.6 seems to work fine when set to Auto but again instantly fails when set to force LE. If i remove the pairing and retry it seems like it doesn’t even try to communicate over the Bluetooth to re-establish the pairing whereas if I revert to Auto then I get the pop-up asking if I want to accept the pairing and download works.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So no, the new test build is no more broken with Windows 10 than the existing build when it comes to Bluetooth (as far as I am concerned).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>JB</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:subsurface@subsurface-divelog.org">Lubomir I. Ivanov via subsurface</a><br><b>Sent: </b>23 June 2020 13:33<br><b>To: </b><a href="mailto:subsurface@subsurface-divelog.org">Subsurface Mailing List</a><br><b>Subject: </b>Re: Request for testers</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>hello everyone,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>could you please try an older version of Subsurface such as:</p><p class=MsoNormal>http://subsurface-divelog.org/downloads/subsurface-4.9.6.exe</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>to ensure that it works for you and that the build change we are</p><p class=MsoNormal>introducing here is not what is the cause for the BLE failures.</p><p class=MsoNormal>note that you need to first uninstall the existing version of</p><p class=MsoNormal>Subsurface before trying a new install.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>also note that the native Windows BLE backend that Subsurface uses has</p><p class=MsoNormal>a number of issues which are out of our control.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>you must:</p><p class=MsoNormal>- install the latest drivers for your device.</p><p class=MsoNormal>- update Windows 10 to the latest version, older versions of Windows</p><p class=MsoNormal>have issues / are unlikely to work.</p><p class=MsoNormal>- use "force LE" when scanning for devices.</p><p class=MsoNormal>- if a device fails to connect try to unpair it, pair again, try to</p><p class=MsoNormal>download again.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>thank you for taking the time to test.</p><p class=MsoNormal>lubomir</p><p class=MsoNormal>--</p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>subsurface mailing list</p><p class=MsoNormal>subsurface@subsurface-divelog.org</p><p class=MsoNormal>http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>