USB (Cressi) Dive Computer Download Support on Mobille app

1,222 views
Skip to first unread message

Eddie Brenton

unread,
Jun 19, 2018, 2:51:31 PM6/19/18
to Subsurface Divelog
Are there any plans to add support for USB dive computer downloads on the mobile app.

I have tested a competitor app (DiveMate) and it does allow me to download directly from my Cressi Giotto using the Cressi USB interface connected directly to my Samsung S8, so I know it is technically possible.

Currently I am loading the data from my Cressi computer to the PC and syncing via the cloud, which works well, but when traveling it would be very nice to be able to load data directly from my computer to the mobile app.

If this has not already been considered I would like to add this as a feature request.

Thank you,
Eddie

Dirk Hohndel

unread,
Jun 19, 2018, 6:29:18 PM6/19/18
to subsurfac...@googlegroups.com
I would like to take a gentle issue with your wording.
You have tested a commercial app. Subsurface-mobile is an open source project, done by volunteers in their spare time.
We don''t have paid developer whom we can tell to chase down certain issues.
As a result, we don't consider ourselves "competitors" with commercial apps - it's simply a very different model, each with very different strengths and weaknesses.

Yes, this has been considered, yes, we roughly know what it would take to do this, no, I don't think anyone with the required skills has the time and motivation to work on this.

Such is life in open source projects.

/D

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/94a4f49e-a869-4fa7-95f4-a4e846eeb2c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Eddie Brenton

unread,
Jun 20, 2018, 11:45:00 AM6/20/18
to Subsurface Divelog
Apologies if my wording offended you Dirk.
My intention was only to indicate that the hardware supports usb downloads and to give an example that developers can look at and possibly utilize in some way.

On Tuesday, June 19, 2018 at 6:29:18 PM UTC-4, Dirk wrote:
I would like to take a gentle issue with your wording.
You have tested a commercial app. Subsurface-mobile is an open source project, done by volunteers in their spare time.
We don''t have paid developer whom we can tell to chase down certain issues.
As a result, we don't consider ourselves "competitors" with commercial apps - it's simply a very different model, each with very different strengths and weaknesses.

Yes, this has been considered, yes, we roughly know what it would take to do this, no, I don't think anyone with the required skills has the time and motivation to work on this.

Such is life in open source projects.

/D
On Jun 20, 2018, at 3:51 AM, Eddie Brenton <ehbr...@gmail.com> wrote:

Are there any plans to add support for USB dive computer downloads on the mobile app.

I have tested a competitor app (DiveMate) and it does allow me to download directly from my Cressi Giotto using the Cressi USB interface connected directly to my Samsung S8, so I know it is technically possible.

Currently I am loading the data from my Cressi computer to the PC and syncing via the cloud, which works well, but when traveling it would be very nice to be able to load data directly from my computer to the mobile app.

If this has not already been considered I would like to add this as a feature request.

Thank you,
Eddie

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Dirk Hohndel

unread,
Jun 20, 2018, 2:57:28 PM6/20/18
to subsurfac...@googlegroups.com
Oh, we are well aware that the hardware support this.
As we said here many times, this is simply a matter of lacking the right person with the right skill set, access to the right hardware, and sufficient spare time & interest to work on this.

/D

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

Don Quichotte

unread,
Jun 20, 2018, 4:06:59 PM6/20/18
to Subsurface Divelog
Mobile Phone Samsung Galaxy J5 (2017) | OS Android 7.0 | Subsurface mobile v 2.0.1 (4.7.4.277) | USB OTG | 'Chinese' FTDI module | USB OTG | dive computer Aqualung i200

I had the same issue: with a FTDI module it was not possible to download the dives.
Then I read that it should be working with Subsurface mobile v 2.0.1 (4.7.4.277) and earlier.
So I cleared the cache from my current version and removed it.
Installed Subsurface mobile v 2.0.1 (4.7.4.277) and …
it works like a charm.

Dirk Hohndel

unread,
Jun 20, 2018, 6:04:10 PM6/20/18
to subsurfac...@googlegroups.com
Please don't post the same info to every thread you find. These actually describe very different problems.

At this point three pieces need to fall into place for USB download to work
(a) it needs to be a supported device - right now that's FTDI based cables plus Eon Steel/Core and possibly the Cobalt 2 -- I unfortunately believe the Cressi dive computers don't fall into this category
(b) the Android version on the phone needs to allow access to the /dev directory under Linux - many newer phones prohibit this with SELinux. Until we change the way we access devices, this will prevent our current approach from working
(c) for while an inadvertent bug in our code disabled this feature altogether - the latest beta which should show up in the play store beta channel within the next hour or so should re-enable this

Thanks

/D

mr.qui...@gmail.com

unread,
Jun 22, 2018, 9:19:24 AM6/22/18
to Subsurface Divelog
@ Dirk: I thought Cressi can work with a FTDI cable (I'm not absolute sure because I don't have a Cressi dive computer).
In that case the new beta can be the key to get it up and running.

Op donderdag 21 juni 2018 00:04:10 UTC+2 schreef Dirk:

Dirk Hohndel

unread,
Jun 22, 2018, 6:51:46 PM6/22/18
to subsurfac...@googlegroups.com
There are indeed some third party download cables - but I haven't seen any for the Cressi. That doesn't mean they don't exist, of course.
Yes, if someone finds an FTDI based download cable for the Cressi, this could indeed work,

/D

Eddie Brenton

unread,
Jun 27, 2018, 12:28:03 PM6/27/18
to subsurfac...@googlegroups.com
I do have a cable that can connect my Cressi computer to my phone, and I have confirmed that it can transfer data.
I'm not sure if it meets FTDI standards, but I have used it to transfer data from the dive computer to a different app (which I do not like as much as Subsurface).

What I currently have is the interface "cradle" for the Cressi, connected to a standard USB cable with a USB "C" adapter on the end to connect to my Samsung Galaxy S8.
In Subsurface, Cressi is not listed in the list of computer vendors on the download page but I've tried a few random computers and I can see the activity light flashing on the Cressi "cradle"

I signed up as a beta tester and I currently have version 2.1.0(4.7.8.421) installed.

Two questions:
1. If anyone has ever been able to download data from a Cressi computer, what vendor and dive computer did you select?
2. Where can I access the older versions of the mobile app, like 2.0.1 mentioned above?

Thank you all for your input!

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 27, 2018, 1:42:31 PM6/27/18
to subsurfac...@googlegroups.com

> On Jun 27, 2018, at 9:27 AM, Eddie Brenton <ehbr...@gmail.com> wrote:
>
> I do have a cable that can connect my Cressi computer to my phone, and I have confirmed that it can transfer data.
> I'm not sure if it meets FTDI standards, but I have used it to transfer data from the dive computer to a different app (which I do not like as much as Subsurface).

So when you plug the cable into your computer (not the phone), what driver gets loaded? Depending on the OS the way to look that up unfortunately is different :-(

> What I currently have is the interface "cradle" for the Cressi, connected to a standard USB cable with a USB "C" adapter on the end to connect to my Samsung Galaxy S8.
> In Subsurface, Cressi is not listed in the list of computer vendors on the download page but I've tried a few random computers and I can see the activity light flashing on the Cressi "cradle"
>
> I signed up as a beta tester and I currently have version 2.1.0(4.7.8.421) installed.
>
> Two questions:
> 1. If anyone has ever been able to download data from a Cressi computer, what vendor and dive computer did you select?
> 2. Where can I access the older versions of the mobile app, like 2.0.1 mentioned above?

We have a pending pull request to add the Cressi Leonardo to the Android app.
There appear to be several different download cables and at least one of them is FTDI based so that might work (but I don't recall if the S8 is one of the phones that allows the way Subsurface accesses OTG devices).

While I have some concerns without more information, I guess I won't get that information unless people have a chance to try, so I'll merge that code - this way the next version of Subsurface-mobile will at least allow you to try.

/D

Eddie Brenton

unread,
Jun 27, 2018, 2:06:11 PM6/27/18
to subsurfac...@googlegroups.com
Awesome!
I'll let you know as soon as I test mine.
Thank you!

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 27, 2018, 2:09:39 PM6/27/18
to subsurfac...@googlegroups.com
The new Android beta notification should go out within the next 30 minutes which has this enabled...

/D

Eddie Brenton

unread,
Jun 27, 2018, 4:22:27 PM6/27/18
to subsurfac...@googlegroups.com
Unfortunately, it does not seem to work with my current cable + computer.
I actually have a Cressi Giotto computer but I believe the hardware and software are basically the same as the Leonardo.



--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.
Screenshot_20180627-161801_Subsurface-mobile.jpg

Dirk Hohndel

unread,
Jun 27, 2018, 4:34:38 PM6/27/18
to subsurfac...@googlegroups.com
Screen shots are always a bit hard to parse.
If you go to the About screen you can simply click on the button and copy the complete logs to the clipboard.
Then you can easily paste this into an email (or a post if you are using the web interface for this forum).

From what I can tell from the screen shot it looks like Subsurface-mobile tried to first talk to your dive computer
via Bluetooth instead of FTDI. Did you select FTDI as connection in the drop down? Right away? Or did you have something else selected at first?
And then we see that dive data input error... I wonder what this is all about - maybe the Giotto and Leonardo aren't identical from a download perspective?

I hope that the full log files will tell us more.

Thanks

/D

Eddie Brenton

unread,
Jun 27, 2018, 5:13:41 PM6/27/18
to subsurfac...@googlegroups.com
Ahha.
I was looking for a way to copy/paste the log. Here ya go.
I tried again, multiple times, ensuring that FTDI was selected before attempting to download. When I press download, the amber activity/data light on the Cressi cradle blinks twice and then nothing else. On that other (inferior) app, the amber light flashes continuously for at least a few seconds, even if the computer is not in the cradle. 

Please let me know if I can provide any more info.

---------- subsurface.log ----------
Empty filename passed to function
"0.015: Successfully opened logfile /storage/emulated/0/subsurface.log at Wed Jun 27 17:06:30 2018"
"0.017: Starting Subsurface-mobile:2.1.0(4.7.8.432):Android Oreo (8.0):arm:en-US"
"0.017: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
"0.017: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
"0.017: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.054: Created position source android"
"Set GPS service update interval to 300 s"
"0.055: Set GPS service update interval to 300 s"
"0.055: location service is available"
"0.675: Synchronising data file"
"0.684: Load dives from local cache"
"0.687: Successfully opened dive data"
"0.688: 4 dives loaded from cache"
"0.689: have cloud credentials, but user asked not to connect to network"
"Set GPS service update interval to 300 s"
"0.690: Set GPS service update interval to 300 s"
Using the following font: Roboto
qqwindow devicePixelRatio 2.6259 2.6259
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Leonardo (SERIAL)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 71.9754 149.544
"1.674: AppState changed to active with no save ongoing and no unsaved changes"
"10.266: AppState changed to inactive with no save ongoing and no unsaved changes"
"10.275: AppState changed to active with no save ongoing and no unsaved changes"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
"14.976: DCDownloadThread started for Cressi Leonardo on FTDI"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
Starting download from  ftdi
Starting the thread 0
"31.026: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "maximumWidth"
no new dives downloaded
"31.033: DCDownloadThread finished"
---------- finish ----------


--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Eddie Brenton

unread,
Jun 27, 2018, 5:16:43 PM6/27/18
to subsurfac...@googlegroups.com
Here is a photo of the hardware I am working with. 
20180627_171452.jpg

Dirk Hohndel

unread,
Jun 27, 2018, 7:10:24 PM6/27/18
to subsurfac...@googlegroups.com
Frustratingly your log shows something that Anton had pointed out to me before but that I stupidly missed to follow up on - the libdivecomputer.log was no longer being written.

I am making a new beta which should show up on the play store within the next 30 minutes or so. That should create the libdivecomputer.log again - which is also copied to the clipboard from the About screen.
Once you installed the new beta, could you please try again and send me the log? Hopefully the libdivecomputer log will tell us more why there was a dive data import error.

Thanks and sorry for the inconvenience

/D

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

Stephen Goodall

unread,
Jun 27, 2018, 7:20:37 PM6/27/18
to Subsurface Divelog
Is it worth adding Giotto to that list before the beta goes out? So it can be selected specifically. Maybe they have a difference that libdivecomputer needs to see?
Im on my way to the office so I can do a PR for that (in about an hour) if needed :)

Dirk Hohndel

unread,
Jun 27, 2018, 7:25:24 PM6/27/18
to subsurfac...@googlegroups.com

> On Jun 27, 2018, at 4:20 PM, 'Stephen Goodall' via Subsurface Divelog <subsurfac...@googlegroups.com> wrote:
>
> Is it worth adding Giotto to that list before the beta goes out? So it can be selected specifically. Maybe they have a difference that libdivecomputer needs to see?
> Im on my way to the office so I can do a PR for that (in about an hour) if needed :)

There appears to be absolutely no difference in the libdivecomputer code.
We might as well add them (but not the Edy - that one is different)

/D

Dirk Hohndel

unread,
Jun 27, 2018, 7:37:37 PM6/27/18
to subsurfac...@googlegroups.com

> On Jun 27, 2018, at 4:10 PM, Dirk Hohndel <di...@hohndel.org> wrote:
>
> Frustratingly your log shows something that Anton had pointed out to me before but that I stupidly missed to follow up on - the libdivecomputer.log was no longer being written.

While testing I found another bug (this time with the layout of the download page), so there are two updates to the Android beta app in flight (the first one just hit the Google Play store). Either one of them should be fine to test the Cressi download again.

/D

Eddie Brenton

unread,
Jun 27, 2018, 9:01:07 PM6/27/18
to subsurfac...@googlegroups.com
No inconvenience to me at all.
I appreciate the effort being put in to getting this working. 

Here is the new log...

---------- subsurface.log ----------
Empty filename passed to function
"0.003: Successfully opened logfile /storage/emulated/0/subsurface.log at Wed Jun 27 20:54:15 2018"
"0.003: Starting Subsurface-mobile:2.1.0(4.7.8.435):Android Oreo (8.0):arm:en-US"
"0.003: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
"0.004: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
"0.004: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.013: Created position source android"
"Set GPS service update interval to 300 s"
"0.013: Set GPS service update interval to 300 s"
"0.013: location service is available"
"0.410: Synchronising data file"
"0.414: Load dives from local cache"
"0.415: Successfully opened dive data"
"0.416: 0 dives loaded from cache"
"0.417: have cloud credentials, but user asked not to connect to network"
"Set GPS service update interval to 300 s"
"0.417: Set GPS service update interval to 300 s"
Using the following font: Roboto
qqwindow devicePixelRatio 2.6259 2.6259
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Leonardo (SERIAL)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 71.9754 149.544
"0.981: AppState changed to active with no save ongoing and no unsaved changes"
"13.330: DCDownloadThread started for Cressi Leonardo on FTDI"
Starting download from  ftdi
Starting the thread 0
"29.367: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"29.374: DCDownloadThread finished"



---------- libdivecomputer.log ----------
Subsurface: v4.7.8-435-g478b5de9e706, built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)
INFO: Open: transport=1
INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: RTS: value=1
INFO: DTR: value=1
INFO: Sleep: value=200
INFO: DTR: value=0
INFO: Sleep: value=100
INFO: Purge: direction=3
INFO: Write: size=8, data=7B3132334442417D
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in /data/android/subsurface/libdivecomputer/src/cressi_leonardo.c:319 (cressi_leonardo_device_dump)]
---------- finish ----------


--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Lubomir I. Ivanov

unread,
Jun 27, 2018, 10:05:27 PM6/27/18
to subsurfac...@googlegroups.com
On 28 June 2018 at 02:20, 'Stephen Goodall' via Subsurface Divelog
<subsurfac...@googlegroups.com> wrote:
> Is it worth adding Giotto to that list before the beta goes out? So it can be selected specifically. Maybe they have a difference that libdivecomputer needs to see?
> Im on my way to the office so I can do a PR for that (in about an hour) if needed :)
>

Stephen Goodall,
please send a new PR:
https://github.com/Subsurface-divelog/subsurface/pull/1437#issuecomment-400886879

lubomir
--

Dirk Hohndel

unread,
Jun 28, 2018, 12:00:22 AM6/28/18
to subsurfac...@googlegroups.com
On Jun 27, 2018, at 6:00 PM, Eddie Brenton <ehbr...@gmail.com> wrote:

No inconvenience to me at all.
I appreciate the effort being put in to getting this working. 

:-)

"0.003: Starting Subsurface-mobile:2.1.0(4.7.8.435):Android Oreo (8.0):arm:en-US"

Latest version

"0.003: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"

Latest libdivcomputer

"13.330: DCDownloadThread started for Cressi Leonardo on FTDI"
Starting download from  ftdi
Starting the thread 0
"29.367: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"29.374: DCDownloadThread finished"

So just as before, we failed to communicate with the device.

---------- libdivecomputer.log ----------
Subsurface: v4.7.8-435-g478b5de9e706, built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)

Matches the log above (yay)

INFO: Open: transport=1
INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: RTS: value=1
INFO: DTR: value=1
INFO: Sleep: value=200
INFO: DTR: value=0
INFO: Sleep: value=100
INFO: Purge: direction=3
INFO: Write: size=8, data=7B3132334442417D
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in /data/android/subsurface/libdivecomputer/src/cressi_leonardo.c:319 (cressi_leonardo_device_dump)]

So our first attempt to write to the dive computer already fails to get an answer.
This is simply the command header and we get nothing back.

I'm thinking that this may not be an FTDI cable after all.

Can you install this app your phone?
(I have nothing to do with the app, it's just one that I found that should give us the information about the USB chipset in the cable)

Thanks

/D


Eddie Brenton

unread,
Jun 28, 2018, 7:20:56 AM6/28/18
to subsurfac...@googlegroups.com
I installed the USB Device Info app.
It correctly shows no devices initially then I connected the Cressi cradle and get the following...

Device Info 
Device Path: /dev/bus/usb/001/002
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID:  0403
Vendor Name (reported):  FTDI
Vendor Name (from DB):  Future Technology Devices International, Ltd

Product ID:  6001
Product Name (reported):  FT232R USB UART
Product Name (from DB):  not found

Additional Info 
Interface #0 
Class: Vendor Specific (0xff)
Endpoint: #0
Address        : 0x81 (10000001)
Number         : 1
Direction      : Inbound (0x80)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 000000010
Endpoint: #1
Address        : 0x02 (000000010)
Number         : 2
Direction      : Outbound (0x0)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 000000010

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 28, 2018, 7:27:56 AM6/28/18
to subsurfac...@googlegroups.com
On Jun 28, 2018, at 4:20 AM, Eddie Brenton <ehbr...@gmail.com> wrote:

I installed the USB Device Info app.
It correctly shows no devices initially then I connected the Cressi cradle and get the following...

Device Info 
Device Path: /dev/bus/usb/001/002
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID:  0403
Vendor Name (reported):  FTDI
Vendor Name (from DB):  Future Technology Devices International, Ltd

Product ID:  6001
Product Name (reported):  FT232R USB UART
Product Name (from DB):  not found

Excellent - that's the right cable. It's a bit disappointing that it doesn't set a useful product
name (a Heinrich Weikamp dive computer will tell you its correct product name), but
that's a bit besides the point here...

Of course now I wonder why we don't get a response back from the dive computer. I assume
it's not something silly like "you need to switch the Cressi into download mode or something,
right? You thought of that already...

I'm trying to create a matching log here but am having a few difficulties with the loaner phone
I am using to test this (and of course I'm testing with an OSTC3)...

/D

Eddie Brenton

unread,
Jun 28, 2018, 7:28:24 AM6/28/18
to subsurfac...@googlegroups.com
The last info I posted was from the API tab in the app. Under the Linux tab there are 3 entries. 

1-1
===
Device Info 
Device Path: /sys/bus/usb/devices/1-1/
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID:  0403
Vendor Name (reported):  FTDI
Vendor Name (from DB):  Future Technology Devices International, Ltd
Product ID:  6001
Product Name (reported):  FT232R USB UART
Product Name (from DB):  not found

Additional Info 
USB Version: 2.00
Speed: 12
Protocol: 00
Maximum Power: 90mA
Serial Number: 00013112


usb1
====
Device Info 
Device Path: /sys/bus/usb/devices/usb1/
Device Class: USB Hub (0x9)
Vendor ID:  1d6b
Vendor Name (reported):  Linux 4.4.78-13663186 xhci-hcd
Vendor Name (from DB):  Linux Foundation
Product ID:  0002
Product Name (reported):  xHCI Host Controller
Product Name (from DB):  not found

Additional Info 
USB Version: 2.00
Speed: 480
Protocol: 01
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto


usb2
====
Device Info 
Device Path: /sys/bus/usb/devices/usb2/
Device Class: USB Hub (0x9)
Vendor ID:  1d6b
Vendor Name (reported):  Linux 4.4.78-13663186 xhci-hcd
Vendor Name (from DB):  Linux Foundation
Product ID:  0003
Product Name (reported):  xHCI Host Controller
Product Name (from DB):  not found

Additional Info 
USB Version: 3.00
Speed: 5000
Protocol: 03
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

Stephen Goodall

unread,
Jun 28, 2018, 7:45:31 AM6/28/18
to Subsurface Divelog
I think the product id (6001) is different to the Leonardo (87d0), selecting Giotto might make libdivecomputer use a different PID to open the device.

That change so you can select it has been merged but not sure if it's on the play store yet

Dirk Hohndel

unread,
Jun 28, 2018, 7:59:12 AM6/28/18
to subsurfac...@googlegroups.com

> On Jun 28, 2018, at 4:45 AM, 'Stephen Goodall' via Subsurface Divelog <subsurfac...@googlegroups.com> wrote:
>
> I think the product id (6001) is different to the Leonardo (87d0), selecting Giotto might make libdivecomputer use a different PID to open the device.

6001 is the "default" FTDI PID. I'm guessing this may not be a Cressi original download cable maybe?
I don't think our code should care at all about which of the PIDs is available - it simply tries all of them.

> That change so you can select it has been merged but not sure if it's on the play store yet

No, I haven't made a new app available as I am currently testing a couple of other small changes. But I will do so soon.

/D

Eddie Brenton

unread,
Jun 28, 2018, 9:07:00 AM6/28/18
to subsurfac...@googlegroups.com
If this helps at all...
The USB "cradle" is an original Cressi product. It does not have a visible serial number or model number on it.
It has two led lights. A blue light that indicates power and an amber light that appears to indicate activity or data transfer.

The blue light stays on solid as long as the device is connected to the phone, regardless of app activity.

If I initiate a download using the "other" app and the dive computer is NOT on the cradle, the amber light will flash about 3 times per second continuously (as if it's pinging and waiting for a response, possibly on different PIDs?)
If I do the same thing using Subsurface the amber light blinks just two times and then nothing more.

To be clear, with Subsurface I get the same results if the computer in on the cradle or not, two blinks from the amber light then nothing else.

In the other app, with the computer ON the cradle, the amber blinks one or two times quickly then the light turns on solid once the connection has been established and the data is being transferred to the phone.

I tested again with the computer on the cradle and did a successful download from that other app, then closed all apps opened Subsurface and immediately attempted to perform a download and I get the same results, two flashes on the amber light then nothing.

I hope this helps.
Thank you!


--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 28, 2018, 9:23:16 AM6/28/18
to subsurfac...@googlegroups.com, Anton Lundin, Jef Driesen

> On Jun 28, 2018, at 6:06 AM, Eddie Brenton <ehbr...@gmail.com> wrote:
>
> If this helps at all...
> The USB "cradle" is an original Cressi product. It does not have a visible serial number or model number on it.

Interesting that it doesn't use the typical Cressi PID then.

> It has two led lights. A blue light that indicates power and an amber light that appears to indicate activity or data transfer.
>
> The blue light stays on solid as long as the device is connected to the phone, regardless of app activity.
>
> If I initiate a download using the "other" app and the dive computer is NOT on the cradle, the amber light will flash about 3 times per second continuously (as if it's pinging and waiting for a response, possibly on different PIDs?)
> If I do the same thing using Subsurface the amber light blinks just two times and then nothing more.

I assume that the light reflects that the communication was successfully established. But we clearly fail to do so since we never hear back from the device.

> I tested again with the computer on the cradle and did a successful download from that other app, then closed all apps opened Subsurface and immediately attempted to perform a download and I get the same results, two flashes on the amber light then nothing.

I wish I had an idea what to try next. Maybe Anton or Jef will have other questions to ask or other things to try.
It seems like this should work...

/D

Jef Driesen

unread,
Jun 28, 2018, 9:37:38 AM6/28/18
to Dirk Hohndel, subsurfac...@googlegroups.com, Anton Lundin
On 2018-06-28 15:23, Dirk Hohndel wrote:
>> On Jun 28, 2018, at 6:06 AM, Eddie Brenton <ehbr...@gmail.com>
>> wrote:
>>
>> If this helps at all...
>> The USB "cradle" is an original Cressi product. It does not have a
>> visible serial number or model number on it.
>
> Interesting that it doesn't use the typical Cressi PID then.

It would be a bit strange if they had their own number and then switch
back, but certainly not impossible either.

>> It has two led lights. A blue light that indicates power and an amber
>> light that appears to indicate activity or data transfer.
>>
>> The blue light stays on solid as long as the device is connected to
>> the phone, regardless of app activity.
>>
>> If I initiate a download using the "other" app and the dive computer
>> is NOT on the cradle, the amber light will flash about 3 times per
>> second continuously (as if it's pinging and waiting for a response,
>> possibly on different PIDs?)
>> If I do the same thing using Subsurface the amber light blinks just
>> two times and then nothing more.
>
> I assume that the light reflects that the communication was
> successfully established. But we clearly fail to do so since we never
> hear back from the device.

Difficult to tell what exactly triggers the leds. It's perfectly
possible to send data over a UART with nothing connected to the other
end. So the interface might notice some signal, but that doesn't mean it
also reaching the dive computer. Again, difficult to tell.

>> I tested again with the computer on the cradle and did a successful
>> download from that other app, then closed all apps opened Subsurface
>> and immediately attempted to perform a download and I get the same
>> results, two flashes on the amber light then nothing.
>
> I wish I had an idea what to try next. Maybe Anton or Jef will have
> other questions to ask or other things to try.
> It seems like this should work...

My first reaction would be to double check the contacts. Maybe there is
just some bad connection. That would explain why we don't get any
response back. But of course that doesn't explain why the other
application appears to work just fine.

Jef

Stepfen

unread,
Jun 30, 2018, 9:29:34 AM6/30/18
to Subsurface Divelog
Hi guys.
Just in case I might be of any help.
I have a cressi newton with the divemate fussion IR interface cable which is confirmed (by the USB device info application) to be FTDI (ID: 87d0). My mobile is Xiaomi REDMI 4X.
I just updated to the latest official version of subsurface (2.1.0)
I choose Cressi, Newton and FTDI in the download menu but when I press "download" nothing happens - the "download" button just changes to "retry".

Probably that's irrelevant but subsurface indicates "bluetooth is not enabled" next to the "download", "quit" and "rescan" buttons in the download menu no matter if I have bluetooth on or off.

My logs are attached below.
The very last part (libdivecomputer.log) - No such file or directory-  looks interesting.
Anything I can try?

Thanks

---------- subsurface.log ----------
Empty filename passed to function
"0.009: Successfully opened logfile /storage/emulated/0/
subsurface.log at Sat Jun 30 16:23:27 2018"
"0.022: Starting Subsurface-mobile:2.1.0(4.8.0.0):Android Nougat (7.1):arm:en-GB"
"0.022: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
"0.022: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
"0.022: built with libgit2 0.26.0"

localBtDevice isn't valid or not connectable
"Created position source android"
"0.038: Created position source android"

"Set GPS service update interval to 300 s"
"0.038: Set GPS service update interval to 300 s"
"0.039: location service is available"
"0.968: Synchronising data file"
"0.973: Load dives from local cache"
"1.078: Successfully opened dive data"
"1.129: AppState changed to active with save ongoing and no unsaved changes"
"1.131: 78 dives loaded from cache"
"1.133: have cloud credentials, trying to connect"
"1.134: Have credentials, let's see if they are valid"
Completed connection with cloud storage backend, response "[OK]"

"Set GPS service update interval to 300 s"
"3.569: Set GPS service update interval to 300 s"

Using the following font: Roboto
qqwindow devicePixelRatio 2 2

Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"

"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 72 147.633
"8.098: Synchronising data file"
"8.149: Sync with cloud storage"
"9.222: Waiting for cloud connection (1 second(s) passed)"
"9.480: Successful cloud connection, fetch remote"
"10.684: Done syncing with cloud storage"
"10.698: Cloud sync shows local cache was current"
"15.944: DCDownloadThread started for Cressi Newton on FTDI"

Starting download from ftdi
Starting the thread 0
Finishing download thread: "Unable to open ftdi Cressi (Newton)"
"15.957: Unsupported operation"
no new dives downloaded
"15.959: DCDownloadThread finished"
The item ScrollablePage_QMLTYPE_23(0xd5465d40, "Log") is already in the PageRow
"45.171: AppState changed to inactive with no save ongoing and no unsaved changes"
"45.369: AppState changed to active with no save ongoing and no unsaved changes"



---------- libdivecomputer.log ----------
Subsurface: v4.8.0, built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)
INFO: Open: name=ftdi
ERROR: No such file or directory (2) [in /data/android/subsurface/libdivecomputer/src/serial_posix.c:295 (dc_serial_open)]
---------- finish ----------

Stephen Goodall

unread,
Jun 30, 2018, 10:40:38 AM6/30/18
to Subsurface Divelog
Does selecting the Leonardo work? It may do if they are similar enough. My Leonardo worked on a OnePlus 3 and using the DiveMate IR

emmdarakis

unread,
Jun 30, 2018, 1:07:36 PM6/30/18
to subsurfac...@googlegroups.com
Nope.  I tried it without success 

On Sat, 30 Jun 2018, 17:40 'Stephen Goodall' via Subsurface Divelog, <subsurfac...@googlegroups.com> wrote:
Does selecting the Leonardo work? It may do if they are similar enough. My Leonardo worked on a OnePlus 3 and using the DiveMate IR

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 30, 2018, 1:32:49 PM6/30/18
to subsurfac...@googlegroups.com

> On Jun 30, 2018, at 6:29 AM, Stepfen <emmda...@gmail.com> wrote:
>
> Hi guys.
> Just in case I might be of any help.
> I have a cressi newton with the divemate fussion IR interface cable which is confirmed (by the USB device info application) to be FTDI (ID: 87d0). My mobile is Xiaomi REDMI 4X.
> I just updated to the latest official version of subsurface (2.1.0)
> I choose Cressi, Newton and FTDI in the download menu but when I press "download" nothing happens - the "download" button just changes to "retry".
>
> Probably that's irrelevant but subsurface indicates "bluetooth is not enabled" next to the "download", "quit" and "rescan" buttons in the download menu no matter if I have bluetooth on or off.

Interesting that it doesn't detect your BT connection. I wonder what Xiaomi is doing different there.

> My logs are attached below.
> The very last part (libdivecomputer.log) - No such file or directory- looks interesting.

Yep

> Anything I can try?

Not really. Your phone rejects the way we currently open USB devices - quite a few phones do that, sadly.
We need to change the way we open USB devices in Subsurface-mobile on Android. But no one has had the time to work on this so far.

> "0.022: Starting Subsurface-mobile:2.1.0(4.8.0.0):Android Nougat (7.1):arm:en-GB"
> "0.022: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
> "0.022: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
> "0.022: built with libgit2 0.26.0"

Current version. Good.

> localBtDevice isn't valid or not connectable

Here's where Qt tells us that you have no working BT.

> "15.944: DCDownloadThread started for Cressi Newton on FTDI"
> Starting download from ftdi
> Starting the thread 0
> Finishing download thread: "Unable to open ftdi Cressi (Newton)"
> "15.957: Unsupported operation"

We weren't allowed to open the FTDI device. That's typically the symptom of SELinux disallowing our access to /dev on the phone.
Nothing we can do right now.

> ---------- libdivecomputer.log ----------
> Subsurface: v4.8.0, built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)
> INFO: Open: name=ftdi
> ERROR: No such file or directory (2) [in /data/android/subsurface/libdivecomputer/src/serial_posix.c:295 (dc_serial_open)]
> ---------- finish ----------

The FTDI open failed, we fell through and tried to open a filename 'ftdi' and that of course failed as well.

/D

emmdarakis

unread,
Jun 30, 2018, 2:26:57 PM6/30/18
to subsurfac...@googlegroups.com
Thanks for the info. I knew it works only for some devices.  I didn't know if I was lucky.
I wish I could help but I'm not a developer. 

Thanks a lot anyway.  Congratulations for your work so far and  keep it up 

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/47N7gaCV_ik/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

Dirk Hohndel

unread,
Jun 30, 2018, 3:00:40 PM6/30/18
to subsurfac...@googlegroups.com

> On Jun 30, 2018, at 11:26 AM, emmdarakis <emmda...@gmail.com> wrote:
>
> Thanks for the info. I knew it works only for some devices. I didn't know if I was lucky.
> I wish I could help but I'm not a developer.

Well, I have started to play with this to see if I can make it work. I now have a device
where it already works, and lots of devices where it doesn't. And I'm reading through
the Android docs and through the Java / JNI stuff to hook this all together.

No promises, but I'll try.

> Thanks a lot anyway. Congratulations for your work so far and keep it up

Thanks! We will. This is the joint work of a lot of people.

/D

divinh

unread,
Aug 4, 2018, 8:50:04 AM8/4/18
to Subsurface Divelog
Hi!

I'm in the beta program.  Hopefully this is another data point to work with...

BlackBerry KEYone running Android 7.1.1, Kernel version 3.18.31-perf-g55f8230 (if any relevance)

USB type C USB-OTG connector between Cressi PC Link and KEYone
     - USB-OTG cable tested with SD card reader and works
     - USB cable is the one that was included with Cressi PC Link and downloads to GNU/Linux boxen works

Subsurface-mobile Version 2.1.0(4.8.0.0)

Usage order:
- plugged in Cressi PC Link
- KEYone automatically asks if Subsurface-mobile should be started, OK
- local data file loaded
- Settings->Display Developer menu, toggle ON
- selected Download from DC icon
- Vendor name: Cressi, Dive Computer: Giotto, Connection: FTDI
    (Prior to the beta version, Cressi and Giotto weren't even options, FTDI needed to be selected each time the app starts up, whereas Cressi and Giotto are remembered.)
- "Download Quit Rescan Bluetooth is not enabled"
- Download
- "Retry Quit Rescan Bluetooth is not enabled"
- About->Copy logs to clipboard

---------- subsurface.log ----------
Empty filename passed to function
"0.006: Failed to open logfile /storage/emulated/0/subsurface.log at Sat Aug 4 05:11:59 2018 error: Permission denied"
"0.007: Failed to open logfile /storage/emulated/0/Documents/subsurface.log at Sat Aug 4 05:11:59 2018 error: Permission denied"
"0.007: Successfully opened logfile /storage/emulated/0/Android/data/org.subsurfacedivelog.mobile/files/Documents/subsurface.log at Sat Aug 4 05:11:59 2018"
"0.009: Starting Subsurface-mobile:2.1.0(4.8.0.0):Android Nougat (7.1):arm:en-US"
"0.009: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
"0.009: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
"0.009: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.019: Created position source android"
"Set GPS service update interval to 300 s"
"0.020: Set GPS service update interval to 300 s"
"0.020: location service is available"
"0.819: Synchronising data file"
"0.836: Load dives from local cache"
"0.952: Successfully opened dive data"
"0.999: AppState changed to active with save ongoing and no unsaved changes"
"1.001: 79 dives loaded from cache"
"1.003: have cloud credentials, but user asked not to connect to network"
"Set GPS service update interval to 300 s"
"1.005: Set GPS service update interval to 300 s"
Using the following font: Roboto
qqwindow devicePixelRatio 2.62667 2.62667
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 71.9542 165.336
"16.935: DCDownloadThread started for Cressi Giotto on FTDI"
Starting download from ftdi
Starting the thread 0
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"16.947: Unsupported operation"
no new dives downloaded
"16.949: DCDownloadThread finished"

divinh

unread,
Aug 5, 2018, 4:29:09 AM8/5/18
to Subsurface Divelog
No problem starting FTDI on another device, but still no download when it works with a GNU/Linux boxen...

Dell Venue 8 7840 running Android 5.1

USB mini USB-OTG connector between Cressi PC Link and Dell 7840
     - USB-OTG cable tested with SD card reader and works
     - USB cable is the one that was included with Cressi PC Link and downloads to GNU/Linux boxen works

Subsurface-mobile Version 2.1.0(4.8.0.0)

Usage order:
- had instant crashes when Subsurface-mobile started, so cleared caches
- entered credentials and cloud data reloaded
- plugged in Cressi PC Link
- 7840 automatically asks if Subsurface-mobile should be started, OK
- Settings->Display Developer menu, toggle ON
- selected Download from DC icon
- Vendor name: Cressi, Dive Computer: Giotto, Connection: FTDI
    (Prior to the beta version, Cressi and Giotto weren't even options, FTDI needed to be selected each time the app starts up, whereas Cressi and Giotto are remembered.)
- "Download Quit Rescan Bluetooth is not enabled"
- Download
- progress bar does something, but Yellow data transfer light flashes really quick a few times, then goes off, unlike when using a GNU/Linux Boxen where the Yellow data light goes for a while as data is transfered
- "Retry Quit Rescan Info: No new dives downloaded from dive computer"
- Retry a few times
- About->Copy logs to clipboard

---------- subsurface.log ----------
Empty filename passed to function
"0.299: Successfully opened logfile /storage/emulated/0/subsurface.log at Sun Aug 5 00:35:52 2018"
"0.322: Starting Subsurface-mobile:2.1.0(4.8.0.0):Android Lollipop (5.1):arm:en-US"
"0.323: built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)"
"0.324: built with Qt Version 5.10.1, runtime from Qt Version 5.10.1"
"0.325: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.356: Created position source android"
"Set GPS service update interval to 300 s"
"0.358: Set GPS service update interval to 300 s"
"0.359: location service is available"
"4.098: no cloud credentials"
"Set GPS service update interval to 300 s"
"4.105: Set GPS service update interval to 300 s"
Using the following font: Roboto
qqwindow devicePixelRatio 2 2
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 72 168.252
"7.264: AppState changed to active with no save ongoing and no unsaved changes"
"25.321: local save requested with no unsaved changes"
"25.455: Synchronising data file"
"27.397: Transfer from storage (0/60)"
"27.425: Transfer from storage (1/60)"
"27.434: Transfer from storage (2/60)"
"27.441: Transfer from storage (3/60)"
"27.448: Transfer from storage (4/60)"
"27.460: Transfer from storage (5/60)"
"27.466: Transfer from storage (6/60)"
"27.472: Transfer from storage (7/60)"
"27.478: Transfer from storage (8/60)"
"27.485: Transfer from storage (9/60)"
"27.491: Transfer from storage (10/60)"
"27.503: Transfer from storage (11/60)"
"27.509: Transfer from storage (12/60)"
"27.514: Transfer from storage (13/60)"
"27.520: Transfer from storage (14/60)"
"27.524: Transfer from storage (15/60)"
"27.529: Transfer from storage (16/60)"
"27.535: Transfer from storage (17/60)"
"27.540: Transfer from storage (18/60)"
"27.546: Transfer from storage (19/60)"
"27.551: Transfer from storage (20/60)"
"27.556: Transfer from storage (21/60)"
"27.562: Transfer from storage (22/60)"
"27.566: Transfer from storage (23/60)"
"27.572: Transfer from storage (24/60)"
"27.578: Transfer from storage (25/60)"
"27.582: Transfer from storage (26/60)"
"27.587: Transfer from storage (27/60)"
"27.591: Transfer from storage (28/60)"
"27.595: Transfer from storage (29/60)"
"27.599: Transfer from storage (30/60)"
"27.602: Transfer from storage (31/60)"
"27.606: Transfer from storage (32/60)"
"27.609: Transfer from storage (33/60)"
"27.612: Transfer from storage (34/60)"
"27.617: Transfer from storage (35/60)"
"27.620: Transfer from storage (36/60)"
"27.624: Transfer from storage (37/60)"
"27.627: Transfer from storage (38/60)"
"27.631: Transfer from storage (39/60)"
"27.635: Transfer from storage (40/60)"
"27.638: Transfer from storage (41/60)"
"27.641: Transfer from storage (42/60)"
"27.646: Transfer from storage (43/60)"
"27.650: Transfer from storage (44/60)"
"27.655: Transfer from storage (45/60)"
"27.659: Transfer from storage (46/60)"
"27.663: Transfer from storage (47/60)"
"27.666: Transfer from storage (48/60)"
"27.669: Transfer from storage (49/60)"
"27.673: Transfer from storage (50/60)"
"27.676: Transfer from storage (51/60)"
"27.678: Transfer from storage (52/60)"
"27.681: Transfer from storage (53/60)"
"27.685: Transfer from storage (54/60)"
"27.688: Transfer from storage (55/60)"
"27.691: Transfer from storage (56/60)"
"27.694: Transfer from storage (57/60)"
"27.696: Transfer from storage (58/60)"
"27.699: Transfer from storage (59/60)"
"27.702: Transfer from storage (60/60)"
"27.707: Transfer from storage (61/80)"
"27.712: Transfer from storage (62/80)"
"27.715: Transfer from storage (63/80)"
"27.720: Transfer from storage (64/80)"
"27.724: Transfer from storage (65/80)"
"27.727: Transfer from storage (66/80)"
"27.731: Transfer from storage (67/80)"
"27.734: Transfer from storage (68/80)"
"27.737: Transfer from storage (69/80)"
"27.740: Transfer from storage (70/80)"
"27.743: Transfer from storage (71/80)"
"27.746: Transfer from storage (72/80)"
"27.748: Transfer from storage (73/80)"
"27.751: Transfer from storage (74/80)"
"27.753: Transfer from storage (75/80)"
"27.755: Transfer from storage (76/80)"
"27.758: Transfer from storage (77/80)"
"27.760: Transfer from storage (78/80)"
"27.762: Transfer from storage (79/80)"
"27.764: Transfer from storage (80/80)"
"28.026: Load dives from local cache"
"28.497: Successfully opened dive data"
"28.586: 79 dives loaded from cache"
"28.595: have cloud credentials, trying to connect"
"28.597: Have credentials, let's see if they are valid"
Completed connection with cloud storage backend, response "[OK]"
"31.645: calling getUserid with user XXXXXXXXXX"
called getUserid
"received WebserviceID:CFQ2B64FNG4FCAQ5JGUFNZADD9LV0H"
"32.049: received WebserviceID:CFQ2B64FNG4FCAQ5JGUFNZADD9LV0H"
"32.072: Synchronising data file"
"32.105: Sync with cloud storage"
"32.489: Successful cloud connection, fetch remote"
"32.712: Done syncing with cloud storage"
"32.732: Cloud sync shows local cache was current"
"96.493: DCDownloadThread started for Cressi Giotto on FTDI"
Starting download from  ftdi
Starting the thread 0
"112.522: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"112.590: DCDownloadThread finished"
"128.486: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Starting the thread 0
"144.687: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"144.854: DCDownloadThread finished"
"190.381: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Starting the thread 0
"206.437: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"206.496: DCDownloadThread finished"
"217.772: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Starting the thread 0
"233.868: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"233.875: DCDownloadThread finished"
"268.604: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Starting the thread 0
"285.212: No new dives downloaded from dive computer"
Finishing download thread: "Dive data import error"
no new dives downloaded
"285.290: DCDownloadThread finished"



---------- libdivecomputer.log ----------
Subsurface: v4.8.0, built with libdivecomputer v0.7.0-devel-Subsurface-NG (02560a7e7fe82919d584d3edbf3876f90382052c)
INFO: Open: transport=1
INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: RTS: value=1
INFO: DTR: value=1
INFO: Sleep: value=200
INFO: DTR: value=0
INFO: Sleep: value=100
INFO: Purge: direction=3
INFO: Write: size=8, data=7B3132334442417D
INFO: Read: size=7, data=7B21443542337D
INFO: Available: value=0
INFO: Read: size=1024, data=04312600FFFFFFFFFFFFFFFFFFFFFFFF010001000000000000000000000000000000000000000000000000000000000000000E15AA260000FF020E15040C0000FF00000000000000000000000000000000000000000000000000000000000000E2002A00220E32424E0100007D070000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0700F000FF00090113011D01FFFFFFFF20012001210121010000210120012101FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0100381438157F001004060A160B040000000300000000000E150E150000FE03F5001B0304320000043200000432000004320000043200000432000004320000043200000432000022FF000000000000010002003A15441684001004060C050C310000020600000000000E150E150000FE03D3001B03043200000E320000C13300003A3A00003E3F0000173E0000913B00001C3800007B3500001F223D010000000001000300461672179500100C0D0A000A320000000100000000000E150E150000FF0339001B030432000004320000043200000432000004320000043200000432000004320000043200000F1FFF000000000001000400741792188E00100C0D0B0B0B3B0000010100000000000E150E150000FE0332001B038A3200005D350000213A0000E93C0000B03B0000AC38000003370000ED340000AA3300000F0F15010000000001000500941890197D00100C0F0A0E0A380000010100000000000E150E15000000049C001C03043200000432000004320000043200000432000004320000043200000432000004320000190FFF0300000000010006009219C81A9A00100C0F0B200C170000010100000000000E150E150000FF0380001C03083200002A3300005F39000079410000A6420000773E0000773B00009437000019350000161923030000000001000700CA1AE61B8D0011041E09110A040000000300000000000E150E150000FD03FE001C020432000004320000043200000432000004320000043200000432000004320000043200002316FF000000000001000800E81BD61C760011041E0B040B2B0000030300000000000E150E150000FC0380001C03043200001532000035340000F53B000008420000C3400000BF3D0000833900005236000016233B010000000001000900D81C141E9D0011050209220A1B0000000700000000000E150E150000FE0300011C030432000004320000043200000432000004320000043200000432000004320000043200002316FF00000B000001000A00161E521F9D001105020C060C3B0000040400000000000E150E150000
INFO: Available: value=176
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in /data/android/subsurface/libdivecomputer/src/cressi_leonardo.c:350 (cressi_leonardo_device_dump)]
---------- finish ----------

Stepfen

unread,
Sep 13, 2018, 3:43:07 PM9/13/18
to Subsurface Divelog
Just to let you know that with the latest beta (4.8.1.412) that I got yesterday when I try to download data to my mobile (Xiaomi Redmi 4x) from my computer (Cressi Newton) with the DiveMate IR cable the app crashes.

With previous versions I couldn't open the FTDI connection but at least the app wouldn't crash.

divinh

unread,
Sep 22, 2018, 1:09:24 AM9/22/18
to Subsurface Divelog
On Lollipop, I get crashes too.  No problem on Oreo.

divinh

unread,
Sep 22, 2018, 1:12:36 AM9/22/18
to Subsurface Divelog
Here's the latest subsurface log on my Dell Venue 7840, running Lollipop, after multiple Retry's...

---------- subsurface.log ----------
Empty filename passed to function
"0.053: Successfully opened logfile /storage/emulated/0/subsurface.log at Fri Sep 21 02:49:55 2018"
"0.067: Starting Subsurface-mobile:2.1.3(4.8.2.5):Android Lollipop (5.1):arm:en-US"
"0.078: built with libdivecomputer v0.7.0-devel-Subsurface-NG (fb70928c83ee09f7a74158d7c316fb18334caf6e)"
"0.079: built with Qt Version 5.11.1, runtime from Qt Version 5.11.1"
"0.086: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.215: Created position source android"
"Set GPS service update interval to 300 s"
"0.217: Set GPS service update interval to 300 s"
QObject::connect: No such signal qPrefLocationService::qPrefLocationService::time_thresholdChanged()
"0.220: location service is available"
"5.093: Synchronising data file"
"5.223: Load dives from local cache"
"5.448: AppState changed to active with save ongoing and no unsaved changes"
"5.739: Successfully opened dive data"
"5.791: 79 dives loaded from cache"
"5.811: have cloud credentials, but user asked not to connect to network"
checkPendingIntents 
Using the following font: Roboto
qqwindow devicePixelRatio 2 2
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL, BT)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"
"Garmin: Descent Mk1 (USBSTORAGE)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE), Smart Air (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT), Teric (BLE)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 72 168.076
"43.971: DCDownloadThread started for Cressi Giotto on FTDI"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"44.025: Input/output error"
no new dives downloaded
"44.030: DCDownloadThread finished"
"62.596: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"62.618: Input/output error"
no new dives downloaded
"62.623: DCDownloadThread finished"
"63.444: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"63.461: Input/output error"
no new dives downloaded
"63.482: DCDownloadThread finished"
"64.274: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"64.292: Input/output error"
no new dives downloaded
"64.316: DCDownloadThread finished"
localBtDevice isn't valid or not connectable
"65.915: DCDownloadThread started for Cressi Giotto on ftdi"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"65.934: Input/output error"
no new dives downloaded
"65.939: DCDownloadThread finished"
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
The item ScrollablePage_QMLTYPE_21(0xedb62340, "Log") is already in the PageRow
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::startTimer: Timers cannot be started from another thread



---------- libdivecomputer.log ----------
Subsurface: v4.8.2-5-g4fc0d9ee132c, built with libdivecomputer v0.7.0-devel-Subsurface-NG (fb70928c83ee09f7a74158d7c316fb18334caf6e)
---------- finish ----------

divinh

unread,
Sep 22, 2018, 1:20:24 AM9/22/18
to Subsurface Divelog
Here's from my BlackBerry KEYone, now running Oreo...

The new thing I notice is the Out of Memory error.

---------- subsurface.log ----------
Empty filename passed to function
"0.005: Failed to open logfile /storage/emulated/0/subsurface.log at Fri Sep 21 02:42:01 2018 error: Permission denied"
"0.005: Failed to open logfile /storage/emulated/0/Documents/subsurface.log at Fri Sep 21 02:42:01 2018 error: Permission denied"
"0.006: Successfully opened logfile /storage/emulated/0/Android/data/org.subsurfacedivelog.mobile/files/Documents/subsurface.log at Fri Sep 21 02:42:01 2018"
"0.006: Starting Subsurface-mobile:2.1.3(4.8.2.5):Android  (8.1):arm:en-US"
"0.006: built with libdivecomputer v0.7.0-devel-Subsurface-NG (fb70928c83ee09f7a74158d7c316fb18334caf6e)"
"0.006: built with Qt Version 5.11.1, runtime from Qt Version 5.11.1"
"0.006: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.016: Created position source android"
"Set GPS service update interval to 300 s"
"0.016: Set GPS service update interval to 300 s"
QObject::connect: No such signal qPrefLocationService::qPrefLocationService::time_thresholdChanged()
"0.016: location service is available"
"0.760: Synchronising data file"
"0.774: Load dives from local cache"
"0.843: Successfully opened dive data"
"0.881: AppState changed to active with save ongoing and no unsaved changes"
"0.882: 79 dives loaded from cache"
"0.884: have cloud credentials, but user asked not to connect to network"
"2.332: UsbDevice[mName=/dev/bus/usb/001/002,mVendorId=1027,mProductId=34768,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=CRESSI,mProductName=CRESSI PC INTERFACE,mVersion=2.0,mSerialNumber=00161161,mConfigurations=[\nUsbConfiguration[mId=1,mName=null,mAttributes=160,mMaxPower=45,mInterfaces=[\nUsbInterface[mId=0,mAlternateSetting=0,mName=CRESSI PC INTERFACE,mClass=255,mSubclass=255,mProtocol=255,mEndpoints=[\nUsbEndpoint[mAddress=129,mAttributes=2,mMaxPacketSize=64,mInterval=0]\nUsbEndpoint[mAddress=2,mAttributes=2,mMaxPacketSize=64,mInterval=0]]]]"
Show download page for device 5;-1;0
done showing download page
checkPendingIntents 
Using the following font: Roboto
qqwindow devicePixelRatio 2.62667 2.62667
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC (SERIAL, BT)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"
"Garmin: Descent Mk1 (USBSTORAGE)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE), Smart Air (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"
"Scubapro: Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE)"
"Seemann: XP5 (SERIAL)"
"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT), Teric (BLE)"
"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"
"Subgear: XP-Air (SERIAL)"
"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"
"Tecdiving: DiveComputer.eu (SERIAL, BT)"
"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"
"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"
qqwindow screen has ldpi/pdpi 71.9542 165.336
"23.143: DCDownloadThread started for Cressi Giotto on FTDI"
Starting download from  ftdi
Finishing download thread: "Unable to open ftdi Cressi (Giotto)"
"23.160: Out of memory"
no new dives downloaded
"23.162: DCDownloadThread finished"
The item ScrollablePage_QMLTYPE_54(0xc9024440, "Log") is already in the PageRow

Stepfen

unread,
Sep 22, 2018, 2:06:48 AM9/22/18
to Subsurface Divelog
I second the new "Out of memory" error with my Xiaomi 4X, Cressi Newton and DiveMate Fusion Ir dongle.

Anton Lundin

unread,
Sep 23, 2018, 3:49:20 PM9/23/18
to Subsurface Divelog
For weird and wonderful reasons, the most relevant log bits ends up directly in adb's logbuffer, and not in our own log buffer. If you're able to do a adb logcat that will tell us for real whats going on, and we should probably figure out how to re-plumb this log messages so they end up in this log...


//Anton

divinh

unread,
Sep 25, 2018, 6:08:18 AM9/25/18
to Subsurface Divelog
How do I go about dumping the adb log buffer?  What's "adb"?

Miika Turkia

unread,
Sep 30, 2018, 11:33:56 PM9/30/18
to Subsurface Divelog
adb comes from Android Debug Bridge and can be used to perform actions on the phone that are not otherwise possible. I.e. run commands, install unsigned applications and inspect the log. You would be running adb on computer and accessing the phone via USB cable or WiFi. More info from:


--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

Daniel Krupp

unread,
Nov 18, 2018, 12:26:52 PM11/18/18
to Subsurface Divelog
Hi All,

I have cressi Newton DC with official cressi USB cable using subsurface version 2.1.5(4.8.4.0).

The download did not start for me either with similar logs as the last one from divinh. The libdivecomputer.log was empty for mee too. 
Did not see any log in the adb logcat either. Is this some bug maybe?

So i recompiled a 4.8.4 and set the __android_log_print loglevel to ANDROID_LOG_INFO in serial_ftdi.c (now the logs are there in Logcat): 
11-18 18:20:59.622 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: in ftdi_open
11-18 18:20:59.622 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: serial_ftdi_open called
11-18 18:20:59.622 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: setting up ftdi_ctx
11-18 18:20:59.623 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: initialize ftdi_ctx
11-18 18:20:59.623 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: call serial_ftdi_open_device
11-18 18:20:59.623 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: serial_ftdi_open_device called
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid 6001 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid 6010 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid 6011 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid 6015 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid f460 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: FTDI tried VID 0403 pid f680 ret -3
11-18 18:20:59.624 7088-7313/org.subsurfacedivelog.mobile I//data/home/dkrupp/src/subsurface/core/serial_ftdi.c: INFO: serial_ftdi_open() failed

This suggests that the cressi PID was not even tried.
So made this patch with which the download from my cressi newton DC works correctly.


Cheers,
Daniel



On Monday, October 1, 2018 at 5:33:56 AM UTC+2, Miika Turkia wrote:
adb comes from Android Debug Bridge and can be used to perform actions on the phone that are not otherwise possible. I.e. run commands, install unsigned applications and inspect the log. You would be running adb on computer and accessing the phone via USB cable or WiFi. More info from:


On Tue, Sep 25, 2018 at 1:08 PM divinh <fxha...@gmail.com> wrote:
How do I go about dumping the adb log buffer?  What's "adb"?

On Sunday, September 23, 2018 at 12:49:20 PM UTC-7, Anton Lundin wrote:
For weird and wonderful reasons, the most relevant log bits ends up directly in adb's logbuffer, and not in our own log buffer. If you're able to do a adb logcat that will tell us for real whats going on, and we should probably figure out how to re-plumb this log messages so they end up in this log...


//Anton

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Lubomir I. Ivanov

unread,
Nov 18, 2018, 1:07:36 PM11/18/18
to subsurfac...@googlegroups.com
On Sun, 18 Nov 2018 at 19:26, Daniel Krupp <danie...@gmail.com> wrote:
>
>
> https://github.com/Subsurface-divelog/subsurface/pull/1863
>

hi, this patch seems sane and i merged it.
thank you.

lubomir
--

divinh

unread,
Jan 14, 2019, 4:08:10 AM1/14/19
to Subsurface Divelog
When would this change take affect?  I'm very curious to see if it fixes issues with the Cressi Giotto as well.

I'm current running Subsurface-mobile 2.1.5(4.8.4.0)

Thanks!

divinh

unread,
Jan 27, 2019, 7:42:15 AM1/27/19
to Subsurface Divelog
I just upgraded to Subsurface-mobile 2.1.6(4.8.4.66) and SUCCESSFULLY download data from my Cressi Giotto!!!

It worked fine with the Dell Venue 8 7000 running Lollipop 5.1.

The BlackBerry KEYone running Oreo 8.1 still has issues, "Out of memory", and that's consistent with my other FTDI dive computer, a Sherwood Vision, i.e. the Vision download works on the Dell Venue 8 7000 Lollipop 5.1 but not the KEYone Oreo 8.1, issuing the same "Out of memory" error.

Thanks for the fix, Daniel Krupp!  And thanks Lubomir for merging it in!

divinh

unread,
May 9, 2020, 8:21:55 AM5/9/20
to Subsurface Divelog
Subsurface-mobile 3.0.5(4.9.3.1486)


Dell Venue 8 7000 Lollipop 5.1
BlackBerry KEYone Oreo 8.1

Cressi Giotto (using FIDI interface)
Sherwood Amphos Air

Downloads work! Thank you!!!
Reply all
Reply to author
Forward
0 new messages