Hi
Was able to reproduce.. It seems like my OSTC sport is detected as OSTC 3.
Hope the log will go through.
Switching manually to OSTC sport results in not being able to download anything.
(log can be sent if needed)

Regards
Werner


On 13 July 2017 3:04:04 pm Dirk Hohndel <[email protected]> wrote:

[bringing this back as a response to the original question]

On Thu, Jul 13, 2017 at 02:01:30PM +0200, Matthias Heinrichs wrote:
Hi,

> From: Werner Macho <[email protected]>
> To: Subsurface Mailing List <[email protected]>
> Subject: Testing v392 with OSTC Sport
> There is no reaction when I switch the Dive Computer to "OSTC Sport" but
> accidentally I hit the retry button while the Dive Computer was set to
> "OSTC 3" and everything worked.

How is the App deciding to which BLE device it's connecting?

It tries to associate Bluetooth names (and the correspondong addresses)
with known patterns for dive computer names. I'm actually surprised that
this didn't end up with an error that it can't determine the address - but
maybe the slightly odd BT names of the OSTC devices worked out in our
favor here and it was misdetected?

Can you reproduce this behavior? If yes, I'd love to see the
subsurface.log for such a successful attempt

To download the logs, both versions (hwOS2 Tech and Sport) are compatible
and the Bluetooth name should not matter. OSTC4 is different, of course.

That's what worries me about this whole thing, TBH. It shouldn't work, and
if it did work, it shouldn't make a difference. So what's going on?

/D
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
"0.000: Successfully opened logfile/storage/emulated/0/subsurface.log"
"0.000: Starting Subsurface-mobile:2.0(4.6.4.392):Android Nougat 
(7.1):arm:en-GB"
"0.000: build with Qt Version 5.9.1, runtime from Qt Version 5.9.1"
"localDevice OnePlus X is valid, starting discovery"
paired Device type 3 with address "00:80:25:49:F9:4D"
paired Device type 3 with address "LE:00:80:25:49:F9:4D"
Found new device: "OSTC 3" "00:80:25:49:F9:4D"
"this could be a Heinrichs Weikamp OSTC family"
adding new btDCs entry (detected DC) "OSTC 3" 4 5 "00:80:25:49:F9:4D"
Found new device: "OSTC 3" "LE:00:80:25:49:F9:4D"
"this could be a Heinrichs Weikamp OSTC family"
adding new btDCs entry (detected DC) "OSTC 3" 4 5 "LE:00:80:25:49:F9:4D"
Paired = "OSTCs 12100" "00:80:25:49:F9:4D"
Paired = "OSTCs 12100" "LE:00:80:25:49:F9:4D"
"Created position source android"
"0.018: Created position source android"
"0.018: location service is available"
getDetectedVendorIndex "" 4
getDetectedProductIndex 5
getDetectedVendorIndex "" 4
getDetectedVendorIndex "" 4
getDetectedProductIndex 5
getDetectedProductIndex 5
getDetectedVendorIndex "Heinrichs Weikamp" 4
getDetectedProductIndex 5
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
"0.631: Switching to no cloud mode"
"0.631: working in no-cloud mode"
"0.633: Load dives from local cache"
"0.649: Successfully opened dive data"
"0.651: 0 dives loaded"
"0.652: working in no-cloud mode, finished loading 0 dives from 
/data/user/0/org.subsurfacedivelog.mobile/files/cloudstorage/localrepo[master]"
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Using the following font: Roboto
qqwindow devicePixelRatio 3 3
qqwindow screen has ldpi/pdpi 72 146.967
"1.486: AppState changed to active with no save ongoing and no unsaved changes"
qrc:/templates/ApplicationHeader.qml:140: TypeError: Cannot read property of 
null
"1.624: Credential scrn: hide kbd was: invisible"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
"16.445: DCDownloadThread started for 00:80:25:49:F9:4D"
Starting download from  BT
Starting the thread 0
connecting to Uuid "{00001101-0000-1000-8000-00805f9b34fb}"
connectToService() "00:80:25:49:F9:4D" "{00001101-0000-1000-8000-00805f9b34fb}"
Connnecting via insecure rfcomm
Connecting socket
"LocalDeviceBroadcastReceiver::onReceive() - event: 
android.bluetooth.device.action.ACL_CONNECTED"
Socket connection established
"17.655: model=OSTC Sport firmware=2597 serial=12100"
"18.777: Dive 1: Sun 4 Jun 2017 12:12"
"19.578: Dive 2: Sun 4 Jun 2017 10:42"
"20.162: Dive 3: Mon 19 Dec 2016 17:22"
Finishing the thread  dives downloaded 3
Executing queued closeSocket()
Executing queued closeSocket()
3 dive downloaded
"20.195: DCDownloadThread finished"
"21.767: Save downloaded dives that were selected"
"21.772: Preparing to save data"
"21.779: Start saving data"
"21.783: Start saving dives"
"21.818: Done creating local cache"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
"LocalDeviceBroadcastReceiver::onReceive() - event: 
android.bluetooth.device.action.ACL_DISCONNECTED"
"26.773: AppState changed to inactive with no save ongoing and no unsaved 
changes"
"26.794: AppState changed to suspended with no save ongoing and no unsaved 
changes"
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to