<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/01/2017 03:18, Rick Walsh wrote:<br>
</div>
<blockquote
cite="mid:CAF+v9JtXCxub1V4TjbfY1Ysq69xQ81_sgCST=i2HmLXtcyv1oA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote"><br>
<div>The greatest feature I can see missing from the mobile
version is downloading from a dive computer. I don't know
m/any people with a Android or iPhone cable that connects
to a dive computer, so Bluetooth / BLE support would be
awesome here. <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<blockquote
cite="mid:CAF+v9JtXCxub1V4TjbfY1Ysq69xQ81_sgCST=i2HmLXtcyv1oA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Cheers,<br>
<br>
</div>
<div>Rick<br>
</div>
</div>
</div>
</div>
</blockquote>
The big single advance over the last few months has been Anton's
implementation of a custom FTDI interface, specifically targeted at
Android. Now that an Android .apk can be built again, I will try
this out again. After quite a bit of testing I suspect my
Android-to-DC cable actually works. Having tested Anton's interface
code in Linux, the next step is to build the full desktop Subsurface
on Android and verify that it works in the Android environment (and
that the cable works). I have a prototype Subsurface-mobile UI
written in Kirigami 1 (Dirk has a copy). After verifying Anton's
FTDI interface on Android, the next step is to use this interface
from within Subsurface-mobile. And all this has to happen without
breaking the Subsurface desktop download from DC. <br>
<br>
I am diving for the next week, but this will be my priority when I
return.<br>
<br>
Kind regards,<br>
willem<br>
<br>
</body>
</html>