Re: Ratio ix3m Pro on Android
On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > Since I'm completely new to diving, let me first thank you all for what > seems to me as the best available divelog! > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to subsurface > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are not > listed, and I can't download the logs to subsurface-mobile (via USB-C > adapter) The Pro models don't support BLE - and on Android support of cable based downloads is mostly non-existant. Yes, for FTDI cables this appears to work for a small number of people who's phones' Android version doesn't block access to the way we try to open the USB port, but it appears for the vast majority of phones even the FTDI download fails. And I /think/ the Ratio download cable isn't FTDI based, anyway. > Is there anything I can do to (help) make it available? > Unfortunately I have never worked with C++ before (well, actually I only > "played lego" with .Net ;-) except of some assembler basics back in school) > I've tried and downloaded the repo, but must admit I do not yet understand > the divecomputer interface, and didn't even find the android related code. > so I fear I can't be much help with actual coding anytime soon We in theory know how this situation could be improved. But the only developer who really seems to fully understand what needs to be done doesn't have the time to work on this, and those who care enough and might have the time, don't have sufficient understanding how to make the libusb2 integration with the native USB port access implementation on newer Android work. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
Dirk, I can ensure you Ratio cable is based on a FTDI FT230X USB to UART converter. Best regards, R.-. On Wed, Sep 11, 2019 at 3:09 PM Dirk Hohndel wrote: > On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > > > Since I'm completely new to diving, let me first thank you all for what > > seems to me as the best available divelog! > > > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to > subsurface > > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are not > > listed, and I can't download the logs to subsurface-mobile (via USB-C > > adapter) > > The Pro models don't support BLE - and on Android support of cable based > downloads is mostly non-existant. Yes, for FTDI cables this appears to > work for a small number of people who's phones' Android version doesn't > block access to the way we try to open the USB port, but it appears for > the vast majority of phones even the FTDI download fails. And I /think/ > the Ratio download cable isn't FTDI based, anyway. > > > Is there anything I can do to (help) make it available? > > Unfortunately I have never worked with C++ before (well, actually I only > > "played lego" with .Net ;-) except of some assembler basics back in > school) > > I've tried and downloaded the repo, but must admit I do not yet > understand > > the divecomputer interface, and didn't even find the android related > code. > > so I fear I can't be much help with actual coding anytime soon > > We in theory know how this situation could be improved. But the only > developer who really seems to fully understand what needs to be done > doesn't have the time to work on this, and those who care enough and might > have the time, don't have sufficient understanding how to make the libusb2 > integration with the native USB port access implementation on newer > Android work. > > /D > ___ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface > -- Riccardo Brama, Ph.D. Chief of Engineering Ratio-Computers, a Dive Industries s.r.l. brand Via Vetturini 22/24 58024 Massa Marittima (GR) Italia Web: www.ratio-computers.com E-mail: riccard...@ratio-computers.com Ai sensi del "Testo Unico sulla Privacy D. Lgs 196 del 30 Giugno 2003" questo messaggio di posta, incluso ogni eventuale allegato, potrebbe contenere materiale riservato, di proprietà esclusiva e/o non pubblico ed e' destinato soltanto alla persona od al soggetto al quale e' indirizzato. E' strettamente vietato modificare, ritrasmettere, divulgare, fare in altro modo uso del messaggio, od intraprendere qualsiasi azione sulla base delle informazioni in esso contenute, da parte di persone diverse dal destinatario. Qualora non foste il destinatario corretto, Vi preghiamo di comunicarlo immediatamente al mittente e di distruggere il presente messaggio da ogni supporto, nonche' ogni stampa o copia dello stesso. According to the "Testo Unico sulla Privacy D. Lgs 196 June 30th 2003" this e-mail, including any attachments, is intended solely for the person or entity to which it is addressed and may contain confidential, proprietary and/or non-public material. Except as stated above, any review, re-transmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than an intended recipient is prohibited. If you receive this in error, please notify the sender and delete the material from any media and destroy any printouts or copies. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On 11 September, 2019 - Dirk Hohndel wrote: > On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > > > Since I'm completely new to diving, let me first thank you all for what > > seems to me as the best available divelog! > > > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to subsurface > > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are not > > listed, and I can't download the logs to subsurface-mobile (via USB-C > > adapter) > > The Pro models don't support BLE - and on Android support of cable based > downloads is mostly non-existant. Yes, for FTDI cables this appears to > work for a small number of people who's phones' Android version doesn't > block access to the way we try to open the USB port, but it appears for > the vast majority of phones even the FTDI download fails. And I /think/ > the Ratio download cable isn't FTDI based, anyway. > Which serial chip do they use? Plug the dive computer into your phone and run a app like: https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator And send the info here, and I'll tell you. > > Is there anything I can do to (help) make it available? > > Unfortunately I have never worked with C++ before (well, actually I only > > "played lego" with .Net ;-) except of some assembler basics back in school) > > I've tried and downloaded the repo, but must admit I do not yet understand > > the divecomputer interface, and didn't even find the android related code. > > so I fear I can't be much help with actual coding anytime soon > > We in theory know how this situation could be improved. But the only > developer who really seems to fully understand what needs to be done > doesn't have the time to work on this, and those who care enough and might > have the time, don't have sufficient understanding how to make the libusb2 > integration with the native USB port access implementation on newer > Android work. Any year now. //Anton -- Anton Lundin+46702-161604 ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Wed, Sep 11, 2019 at 4:45 PM Anton Lundin wrote: > On 11 September, 2019 - Dirk Hohndel wrote: > > > On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > > > > > Since I'm completely new to diving, let me first thank you all for what > > > seems to me as the best available divelog! > > > > > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to > subsurface > > > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are not > > > listed, and I can't download the logs to subsurface-mobile (via USB-C > > > adapter) > > > > The Pro models don't support BLE - and on Android support of cable based > > downloads is mostly non-existant. Yes, for FTDI cables this appears to > > work for a small number of people who's phones' Android version doesn't > > block access to the way we try to open the USB port, but it appears for > > the vast majority of phones even the FTDI download fails. And I /think/ > > the Ratio download cable isn't FTDI based, anyway. > > > > Which serial chip do they use? > > Plug the dive computer into your phone and run a app like: > https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator > > And send the info here, and I'll tell you. > Like Ricardo wrote: FTDI FT230X Basic UART 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: 6015 Product Name (reported): FT230X Basic UART Product Name (from DB): not found Additional Info Interface #0 Class: Vendor Specific (0xff) Endpoint: #0 Address: 0x81 (1001) Number : 1 Direction : Inbound (0x80) Type : Bulk (0x2) Poll Interval : 0 Max Packet Size: 64 Attributes : 00010 Endpoint: #1 Address: 0x02 (00010) Number : 2 Direction : Outbound (0x0) Type : Bulk (0x2) Poll Interval : 0 Max Packet Size: 64 Attributes : 00010 > > > > Is there anything I can do to (help) make it available? > > > Unfortunately I have never worked with C++ before (well, actually I > only > > > "played lego" with .Net ;-) except of some assembler basics back in > school) > > > I've tried and downloaded the repo, but must admit I do not yet > understand > > > the divecomputer interface, and didn't even find the android related > code. > > > so I fear I can't be much help with actual coding anytime soon > > > > We in theory know how this situation could be improved. But the only > > developer who really seems to fully understand what needs to be done > > doesn't have the time to work on this, and those who care enough and > might > > have the time, don't have sufficient understanding how to make the > libusb2 > > integration with the native USB port access implementation on newer > > Android work. > OK, thanks. My phone does react kind of unexpected when I try to change the USB mode from client to OTG (switching back stating couldn't switch) So a workaround might be using an old android device as a downloader? Or wouldn't this work anyways since the ProductID isn't implemented on subsurface-mobile? Well, on the other hand, downloading the dive shouldn't be so urgent that it can't wait until I'm back on a real computer. - Since I'm not into tech diving (yet) ;-) thanks again for your help and all the work! best regards Benji ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On 11 September, 2019 - liquid tcp wrote: > On Wed, Sep 11, 2019 at 4:45 PM Anton Lundin wrote: > > > On 11 September, 2019 - Dirk Hohndel wrote: > > > > > On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > > > > > > > Since I'm completely new to diving, let me first thank you all for what > > > > seems to me as the best available divelog! > > > > > > > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to > > subsurface > > > > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are not > > > > listed, and I can't download the logs to subsurface-mobile (via USB-C > > > > adapter) > > > > > > The Pro models don't support BLE - and on Android support of cable based > > > downloads is mostly non-existant. Yes, for FTDI cables this appears to > > > work for a small number of people who's phones' Android version doesn't > > > block access to the way we try to open the USB port, but it appears for > > > the vast majority of phones even the FTDI download fails. And I /think/ > > > the Ratio download cable isn't FTDI based, anyway. > > > > > > > Which serial chip do they use? > > > > Plug the dive computer into your phone and run a app like: > > https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator > > > > And send the info here, and I'll tell you. > > > > Like Ricardo wrote: FTDI FT230X Basic UART > > 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: 6015 > Product Name (reported): FT230X Basic UART > Product Name (from DB): not found Then its just our filter logic that needs updating. I'd love to be able to disable that logic for cases like this, and just show everything and let the user pick what device and communication method. Like we have the ShowNonDiveComputers , we should have a show all dive computers, even if they probably don't work. > > > > > > > Is there anything I can do to (help) make it available? > > > > Unfortunately I have never worked with C++ before (well, actually I > > only > > > > "played lego" with .Net ;-) except of some assembler basics back in > > school) > > > > I've tried and downloaded the repo, but must admit I do not yet > > understand > > > > the divecomputer interface, and didn't even find the android related > > code. > > > > so I fear I can't be much help with actual coding anytime soon > > > > > > We in theory know how this situation could be improved. But the only > > > developer who really seems to fully understand what needs to be done > > > doesn't have the time to work on this, and those who care enough and > > might > > > have the time, don't have sufficient understanding how to make the > > libusb2 > > > integration with the native USB port access implementation on newer > > > Android work. > > > > OK, thanks. My phone does react kind of unexpected when I try to change the > USB mode from client to OTG (switching back stating couldn't switch) > So a workaround might be using an old android device as a downloader? Or > wouldn't this work anyways since the ProductID isn't implemented on > subsurface-mobile? Sounds like your phone isn't that healthy. OTG is a requirement to be able to download from a ftdi device. All the bits are there, just that the Ratio dc's isn't in the list of known ftdi dive computers. > Well, on the other hand, downloading the dive shouldn't be so urgent that > it can't wait until I'm back on a real computer. - Since I'm not into tech > diving (yet) ;-) Downloading from a dc and tech diving have no correlation. Downloading data from your dc and keeping that in your logbook is one thing, tech diving is another thing. //Anton - Who thinks "Technical diving" is a really bad name -- Anton Lundin+46702-161604 ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Thu, Sep 12, 2019 at 10:25 AM Anton Lundin wrote: > On 11 September, 2019 - liquid tcp wrote: > > > On Wed, Sep 11, 2019 at 4:45 PM Anton Lundin wrote: > > > > > On 11 September, 2019 - Dirk Hohndel wrote: > > > > > > > On Wed, Sep 11, 2019 at 09:07:51AM +0200, liquid tcp wrote: > > > > > > > > > > Since I'm completely new to diving, let me first thank you all for > what > > > > > seems to me as the best available divelog! > > > > > > > > > > I do have a Ratio ix3m Pro (Deep) computer that downloads fine to > > > subsurface > > > > > In the Android app [2.2.0(4.9.1.40) - playstore beta] the pros are > not > > > > > listed, and I can't download the logs to subsurface-mobile (via > USB-C > > > > > adapter) > > > > > > > > The Pro models don't support BLE - and on Android support of cable > based > > > > downloads is mostly non-existant. Yes, for FTDI cables this appears > to > > > > work for a small number of people who's phones' Android version > doesn't > > > > block access to the way we try to open the USB port, but it appears > for > > > > the vast majority of phones even the FTDI download fails. And I > /think/ > > > > the Ratio download cable isn't FTDI based, anyway. > > > > > > > > > > Which serial chip do they use? > > > > > > Plug the dive computer into your phone and run a app like: > > > > https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator > > > > > > And send the info here, and I'll tell you. > > > > > > > Like Ricardo wrote: FTDI FT230X Basic UART > > > > 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: 6015 > > Product Name (reported): FT230X Basic UART > > Product Name (from DB): not found > > Then its just our filter logic that needs updating. > > I'd love to be able to disable that logic for cases like this, and just > show everything and let the user pick what device and communication > method. Like we have the ShowNonDiveComputers , we should have a show > all dive computers, even if they probably don't work. > > > > > > > > > > > Is there anything I can do to (help) make it available? > > > > > Unfortunately I have never worked with C++ before (well, actually I > > > only > > > > > "played lego" with .Net ;-) except of some assembler basics back in > > > school) > > > > > I've tried and downloaded the repo, but must admit I do not yet > > > understand > > > > > the divecomputer interface, and didn't even find the android > related > > > code. > > > > > so I fear I can't be much help with actual coding anytime soon > > > > > > > > We in theory know how this situation could be improved. But the only > > > > developer who really seems to fully understand what needs to be done > > > > doesn't have the time to work on this, and those who care enough and > > > might > > > > have the time, don't have sufficient understanding how to make the > > > libusb2 > > > > integration with the native USB port access implementation on newer > > > > Android work. > > > > > > > OK, thanks. My phone does react kind of unexpected when I try to change > the > > USB mode from client to OTG (switching back stating couldn't switch) > > So a workaround might be using an old android device as a downloader? Or > > wouldn't this work anyways since the ProductID isn't implemented on > > subsurface-mobile? > > Sounds like your phone isn't that healthy. OTG is a requirement to be > able to download from a ftdi device. > > All the bits are there, just that the Ratio dc's isn't in the list of > known ftdi dive computers. > > OTG is working fine with other devices. So i /think/ that is what Dirk meant with Android blocking the way we access the USB. I do have an older phone lying around in the office. I'll take it home and see whether it behaves differently > Well, on the other hand, downloading the dive shouldn't be so urgent that > > it can't wait until I'm back on a real computer. - Since I'm not into > tech > > diving (yet) ;-) > > Downloading from a dc and tech diving have no correlation. Downloading > data from your dc and keeping that in your logbook is one thing, tech > diving is another thing. > > //Anton - Who thinks "Technical diving" is a really bad name > > What I meant to say: I don't need the detailed data for planning my next dive. on the other hand, if I needed I'd most likely prefer a Notebook anyways ;-) Should I better say extended range? best regards Benji ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Wed, Sep 11, 2019 at 11:53:48PM +0200, liquid tcp wrote:
> >
> > Which serial chip do they use?
> >
> > Plug the dive computer into your phone and run a app like:
> > https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator
> >
> > And send the info here, and I'll tell you.
> >
>
> Like Ricardo wrote: FTDI FT230X Basic UART
>
> 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: 6015
> Product Name (reported): FT230X Basic UART
> Product Name (from DB): not found
So that's one of the chips that we already detect. When you plug this into
your phone, are you asked if you want to open Subsurface-mobile?
It's quite easy to create a beta version of Subsurace that includes the
Ratio dive computers as supported on Android to make it possile for you to
test this. Do all "Pro" computers use the same cable?
{"DiveSystem", "Orca", DC_FAMILY_DIVESYSTEM_IDIVE, 0x02,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x03,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive DAN", DC_FAMILY_DIVESYSTEM_IDIVE, 0x04,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Tech",DC_FAMILY_DIVESYSTEM_IDIVE, 0x05,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x06,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Stealth", DC_FAMILY_DIVESYSTEM_IDIVE, 0x07,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x08,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x09,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive X3M", DC_FAMILY_DIVESYSTEM_IDIVE, 0x0A,
DC_TRANSPORT_SERIAL, NULL},
{"DiveSystem", "iDive Deep",DC_FAMILY_DIVESYSTEM_IDIVE, 0x0B,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M GPS Pro ", DC_FAMILY_DIVESYSTEM_IDIVE, 0x21,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M GPS Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x22,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M GPS Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x23,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M GPS Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x24,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M GPS Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x25,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M GPS Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x26,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
{"Ratio", "iX3M Pro Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x31,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M Pro Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x32,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M Pro Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x33,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M Pro Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x35,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iX3M Pro Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x36,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x40,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Fancy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x41,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x42,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x43,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Deep",DC_FAMILY_DIVESYSTEM_IDIVE, 0x44,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Tech+", DC_FAMILY_DIVESYSTEM_IDIVE, 0x45,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x46,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Free", DC_FAMILY_DIVESYSTEM_IDIVE, 0x50,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x51,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x52,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x53,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x54,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x55,
DC_TRANSPORT_SERIAL, NULL},
{"Ratio", "iDive Color Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x56,
DC_TRANSP
Re: Ratio ix3m Pro on Android
Dirk,
yes all of them share the same cable controller. It should work that way.
Thank you and cheers,
R.-.
Inviato da iPhone di
Eng. Riccardo Brama, Ph.D.
Chief of Engineering @Dive Industries
> Il giorno 12 set 2019, alle ore 17:13, Dirk Hohndel ha
> scritto:
>
> On Wed, Sep 11, 2019 at 11:53:48PM +0200, liquid tcp wrote:
>>>
>>> Which serial chip do they use?
>>>
>>> Plug the dive computer into your phone and run a app like:
>>> https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator
>>>
>>> And send the info here, and I'll tell you.
>>>
>>
>> Like Ricardo wrote: FTDI FT230X Basic UART
>>
>> 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: 6015
>> Product Name (reported): FT230X Basic UART
>> Product Name (from DB): not found
>
> So that's one of the chips that we already detect. When you plug this into
> your phone, are you asked if you want to open Subsurface-mobile?
>
> It's quite easy to create a beta version of Subsurace that includes the
> Ratio dive computers as supported on Android to make it possile for you to
> test this. Do all "Pro" computers use the same cable?
>
>{"DiveSystem", "Orca", DC_FAMILY_DIVESYSTEM_IDIVE, 0x02,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x03,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive DAN", DC_FAMILY_DIVESYSTEM_IDIVE, 0x04,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Tech",DC_FAMILY_DIVESYSTEM_IDIVE, 0x05,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x06,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Stealth", DC_FAMILY_DIVESYSTEM_IDIVE, 0x07,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x08,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x09,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive X3M", DC_FAMILY_DIVESYSTEM_IDIVE, 0x0A,
> DC_TRANSPORT_SERIAL, NULL},
>{"DiveSystem", "iDive Deep",DC_FAMILY_DIVESYSTEM_IDIVE, 0x0B,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M GPS Pro ", DC_FAMILY_DIVESYSTEM_IDIVE, 0x21,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M GPS Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x22,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M GPS Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x23,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M GPS Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x24,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M GPS Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x25,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M GPS Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x26,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
>{"Ratio", "iX3M Pro Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x31,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M Pro Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x32,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M Pro Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x33,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M Pro Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x35,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iX3M Pro Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x36,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x40,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Fancy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x41,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x42,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x43,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Deep",DC_FAMILY_DIVESYSTEM_IDIVE, 0x44,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Tech+", DC_FAMILY_DIVESYSTEM_IDIVE, 0x45,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x46,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Color Free", DC_FAMILY_DIVESYSTEM_IDIVE, 0x50,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Color Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x51,
> DC_TRANSPORT_SERIAL, NULL},
>{"Ratio", "iDive Color Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x52,
> DC_TRANSPORT_SERIAL, NU
Re: Ratio ix3m Pro on Android
On Thu, Sep 12, 2019 at 5:13 PM Dirk Hohndel wrote:
> On Wed, Sep 11, 2019 at 11:53:48PM +0200, liquid tcp wrote:
> > >
> > > Which serial chip do they use?
> > >
> > > Plug the dive computer into your phone and run a app like:
> > >
> https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator
> > >
> > > And send the info here, and I'll tell you.
> > >
> >
> > Like Ricardo wrote: FTDI FT230X Basic UART
> >
> > 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: 6015
> > Product Name (reported): FT230X Basic UART
> > Product Name (from DB): not found
>
> So that's one of the chips that we already detect. When you plug this into
> your phone, are you asked if you want to open Subsurface-mobile?
>
Yes! so this is a good sign then :-)
>
> It's quite easy to create a beta version of Subsurace that includes the
> Ratio dive computers as supported on Android to make it possile for you to
> test this. Do all "Pro" computers use the same cable?
>
For all I know all [Pro] are the same hardware (and upgradeable by firmware
(except of an additional chip for Rebreather)) but I'd wait for Riccardo's
response so we can be sure.
@Riccardo: Do you use the same chip on all devices? and do you have a list
of them? I do find references to an iX3M My16 edition online which are not
yet on the list...
@Dirk: I have to build me a new dev. Environment on Linux before I can
compile it if I remember you correctly. Any recommendations on a good DE?
(been using VS so far...), so I might not make it tonight. but I understand
the changes would be like:
---{"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
DC_TRANSPORT_SERIAL, NULL},
+++ {"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
DC_TRANSPORT_SERIAL, dc_filter_divesystem },
>
> {"DiveSystem", "Orca", DC_FAMILY_DIVESYSTEM_IDIVE, 0x02,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x03,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive DAN", DC_FAMILY_DIVESYSTEM_IDIVE, 0x04,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Tech",DC_FAMILY_DIVESYSTEM_IDIVE, 0x05,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x06,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Stealth", DC_FAMILY_DIVESYSTEM_IDIVE, 0x07,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x08,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x09,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive X3M", DC_FAMILY_DIVESYSTEM_IDIVE, 0x0A,
> DC_TRANSPORT_SERIAL, NULL},
> {"DiveSystem", "iDive Deep",DC_FAMILY_DIVESYSTEM_IDIVE, 0x0B,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M GPS Pro ", DC_FAMILY_DIVESYSTEM_IDIVE, 0x21,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M GPS Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x22,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M GPS Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x23,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M GPS Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x24,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M GPS Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x25,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M GPS Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x26,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH, dc_filter_divesystem},
> {"Ratio", "iX3M Pro Fancy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x31,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M Pro Easy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x32,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M Pro Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x33,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M Pro Tech+",DC_FAMILY_DIVESYSTEM_IDIVE, 0x35,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iX3M Pro Reb", DC_FAMILY_DIVESYSTEM_IDIVE, 0x36,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iDive Free",DC_FAMILY_DIVESYSTEM_IDIVE, 0x40,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iDive Fancy", DC_FAMILY_DIVESYSTEM_IDIVE, 0x41,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iDive Easy",DC_FAMILY_DIVESYSTEM_IDIVE, 0x42,
> DC_TRANSPORT_SERIAL, NULL},
> {"Ratio", "iDive Pro", DC_FAMILY_DIVESYSTEM_IDIVE, 0x43,
> DC_TRANSPORT_SE
Re: Ratio ix3m Pro on Android
On Thu, Sep 12, 2019 at 06:49:39PM +0200, liquid tcp wrote:
> > So that's one of the chips that we already detect. When you plug this into
> > your phone, are you asked if you want to open Subsurface-mobile?
> >
> Yes! so this is a good sign then :-)
Yes - it doesn't mean, though, that your Android device does allow access
to the way we want to access that device :-(
> > It's quite easy to create a beta version of Subsurace that includes the
> > Ratio dive computers as supported on Android to make it possile for you to
> > test this. Do all "Pro" computers use the same cable?
>
> For all I know all [Pro] are the same hardware (and upgradeable by firmware
> (except of an additional chip for Rebreather)) but I'd wait for Riccardo's
> response so we can be sure.
> @Riccardo: Do you use the same chip on all devices? and do you have a list
> of them? I do find references to an iX3M My16 edition online which are not
> yet on the list...
Interesting. What are the differences to the others? What's its model
number?
> @Dirk: I have to build me a new dev. Environment on Linux before I can
> compile it if I remember you correctly. Any recommendations on a good DE?
I tend to use Qt Creator on Linux or macOS. Native building under Windows
isn't supported at all. Creating the Android binaries is easiest done
using our hand crafted docker build container. You can look at our Travis
instructions for Android to see how you can do that.
Check the files in subsurface/scripts/android
> (been using VS so far...), so I might not make it tonight. but I understand
> the changes would be like:
> ---{"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
> DC_TRANSPORT_SERIAL, NULL},
> +++ {"Ratio", "iX3M Pro Deep", DC_FAMILY_DIVESYSTEM_IDIVE, 0x34,
> DC_TRANSPORT_SERIAL, dc_filter_divesystem },
No, that's not it at all...
I need to add code to have these dive computers listsed on Android
devices. I'll do that in a moment and maybe I can just tether through my
phone and upload the binaries. Then you'll be able to install this via the
Google Play Beta channel for Subsurfae-mobile.
Fingers crossed you'll have something there in a few hours.
/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Thu, Sep 12, 2019 at 06:02:38PM +0100, Dirk Hohndel wrote: > > I need to add code to have these dive computers listsed on Android > devices. I'll do that in a moment and maybe I can just tether through my > phone and upload the binaries. Then you'll be able to install this via the > Google Play Beta channel for Subsurfae-mobile. > > Fingers crossed you'll have something there in a few hours. It took more than two hours, but it's now in Google's systems. The time it takes before it then becomes available in the play store appears to be more or less random. But at some point within the next 1-48 hours the new version that tries to enable the Ratio / DiveSystem dive computers on Android should show up as a new beta release. It will identify itself as Subsurface-mobile 2.2.0 (4.9.3.16) /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Thu, Sep 12, 2019 at 8:48 PM Dirk Hohndel wrote: > On Thu, Sep 12, 2019 at 06:02:38PM +0100, Dirk Hohndel wrote: > > > > I need to add code to have these dive computers listsed on Android > > devices. I'll do that in a moment and maybe I can just tether through my > > phone and upload the binaries. Then you'll be able to install this via > the > > Google Play Beta channel for Subsurfae-mobile. > > > > Fingers crossed you'll have something there in a few hours. > > It took more than two hours, but it's now in Google's systems. The time it > takes before it then becomes available in the play store appears to be > more or less random. But at some point within the next 1-48 hours the new > version that tries to enable the Ratio / DiveSystem dive computers on > Android should show up as a new beta release. > > It will identify itself as Subsurface-mobile 2.2.0 (4.9.3.16) > > /D > You ARE incredible! thank you ! I'll post the result as soon as I have it. Benji ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On September 12, 2019 10:59:55 PM GMT+02:00, liquid tcp wrote: > >I'll post the result as soon as I have it. Google tells me the new version is available now to beta testers /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
On Fri, Sep 13, 2019 at 3:03 AM Dirk Hohndel wrote: > > > On September 12, 2019 10:59:55 PM GMT+02:00, liquid tcp < > liquid@gmail.com> wrote: > > > >I'll post the result as soon as I have it. > > Google tells me the new version is available now to beta testers > > Great, thanks so much! I can choose it in the list, but unfortunately don't get any data returned: --- "20.332: DCDownloadThread started for Ratio iX3M Pro Deep on FTDI downloading only new dives" Starting download from ftdi downloading only new dives Finishing download thread: "Unable to open ftdi Ratio (iX3M Pro Deep)" "20.337: Out of memory" no new dives downloaded "20.338: DCDownloadThread finished" ... ... "102.452: DCDownloadThread started for Ratio iX3M Pro Deep on FTDI downloading all dives" Starting download from ftdi downloading all dives "102.454: Out of memory" "102.454: Out of memory" Finishing download thread: "Unable to open ftdi Ratio (iX3M Pro Deep)" 102.507: DCDownloadThread finished" --- I'm trying to get some more detailed data of what's happening btw: Ricardo has replied about the same hardware, but somehow it was sent to me instead of the list: "Pro versions equip the same hardware except for GPS and Bluetooth radios. So yes, same cable. You know, to be as clear as possible: the USB to UART interface is equipped within our cables, not onto the dive computer so yes, you can interact with anyone of them without fearing to imement different drivers. " @riccardo: in the CC transmitter manual you reference a red- and a "blue dot" cable not being compatible for charging. are there also relevant differences for us? Benji ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
Benji, On Fri, Sep 13, 2019 at 9:44 AM liquid tcp wrote: > @riccardo: in the CC transmitter manual you reference a red- and a "blue > dot" cable not being compatible for charging. are there also relevant > differences for us? > They share the same controller but not the same "mechanical" design. So nothing software should be concerned about. ;o) Cheers, R.-. -- Riccardo Brama, Ph.D. Head of Engineering @ Dive Industries S.r.l. IEEE & IEEE-SA Member Linux Registered User #203260 - (I):SWC'06 ISOC Member #93108 Iscr. Albo Ing. BR A1609 M1 Asi-Sub CMAS Dive Instructor Sommelier II livello AIS sez. BR Personal Webspaces: http://www.linkedin.com/in/riccardobrama "And on the sixth day gates went broken and a never ended flock of Penguins flown by to the Great Pure Lands..." ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
Could you try to download again and then go to the "About" page and copy the log files and paste them into an email? From the below it seems that Subsurface-mobile is running out of memory - which is very surprising to me. Yes, it is a bit of a memory hog, bit even on fairly old devices running out of memory is extremely rare... /D On September 13, 2019 9:43:55 AM GMT+02:00, liquid tcp wrote: >On Fri, Sep 13, 2019 at 3:03 AM Dirk Hohndel wrote: > >> >> >> On September 12, 2019 10:59:55 PM GMT+02:00, liquid tcp < >> liquid@gmail.com> wrote: >> > >> >I'll post the result as soon as I have it. >> >> Google tells me the new version is available now to beta testers >> >> Great, thanks so much! >I can choose it in the list, but unfortunately don't get any data >returned: > >--- >"20.332: DCDownloadThread started for Ratio iX3M Pro Deep on FTDI >downloading only new dives" >Starting download from ftdi >downloading only new dives >Finishing download thread: "Unable to open ftdi Ratio (iX3M Pro Deep)" >"20.337: Out of memory" >no new dives downloaded >"20.338: DCDownloadThread finished" >... >... >"102.452: DCDownloadThread started for Ratio iX3M Pro Deep on FTDI >downloading all dives" >Starting download from ftdi >downloading all dives >"102.454: Out of memory" >"102.454: Out of memory" >Finishing download thread: "Unable to open ftdi Ratio (iX3M Pro Deep)" >102.507: DCDownloadThread finished" >--- > >I'm trying to get some more detailed data of what's happening > >btw: Ricardo has replied about the same hardware, but somehow it was >sent >to me instead of the list: > >"Pro versions equip the same hardware except for GPS and Bluetooth >radios. >So yes, same cable. You know, to be as clear as possible: the USB to >UART >interface is equipped within our cables, not onto the dive computer so >yes, >you can interact with anyone of them without fearing to imement >different >drivers. " > >@riccardo: in the CC transmitter manual you reference a red- and a >"blue >dot" cable not being compatible for charging. are there also relevant >differences for us? > > > Benji -- From my phone___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ratio ix3m Pro on Android
> Could you try to download again and then go to the "About" page and copy the log files and paste them into an email? > From the below it seems that Subsurface-mobile is running out of memory - which is very surprising to me. Yes, it is a bit of a memory hog, bit even on fairly old devices running out of memory is extremely rare... > /D sure, here are the logs. just did, to be sure, a reboot and cleaned the memory, so I'm having 2.5GB available with subsurface using 193MB giving me the same behaviour. here the full logs: -- subsurface.log -- "0.003: Failed to open logfile /storage/emulated/0/subsurface.log at Fri Sep 13 13:12:44 2019 error: Permission denied" "0.004: Failed to open logfile /storage/emulated/0/Documents/subsurface.log at Fri Sep 13 13:12:44 2019 error: Permission denied" "0.004: Successfully opened logfile /storage/emulated/0/Android/data/org.subsurfacedivelog.mobile/files/Documents/subsurface.log at Fri Sep 13 13:12:44 2019" "0.004: Starting Subsurface-mobile:2.2.0(4.9.3.16):Android (9.0):arm64:en-US" "0.004: built with libdivecomputer v0.7.0-devel-Subsurface-NG (ce6d9896a79afaa82641132e338f8744714c8593)" "0.004: built with Qt Version 5.12.4, runtime from Qt Version 5.12.4" "0.004: built with libgit2 0.26.0" BTDiscoveryReDiscover: localBtDevice.isValid() true localBtDevice isn't valid or not connectable "Created position source android" "0.014: Created position source android" "Set GPS service update interval to 300 s" "0.015: Set GPS service update interval to 300 s" "0.015: location service is not available" qrc:/org/kde/kirigami/Page.qml:276:5: QML Loader: Binding loop detected for property "active" QQmlExpression: Expression qrc:/qml/DownloadFromDiveComputer.qml:338:5 depends on non-NOTIFYable properties: QMLManager::DC_forceDownload Model size of -1 is less than 0 Both point size and pixel size set. Using pixel size. "0.578: Synchronising data file" "0.584: Load dives from local cache" "0.587: Successfully opened dive data" "0.588: 7 dives loaded from cache" "0.589: have cloud credentials, but user asked not to connect to network" "1.096: UsbDevice[mName=/dev/bus/usb/001/002,mVendorId=1027,mProductId=24597,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=FTDI,mProductName=FT230X Basic UART,mVersion=10.00,mSerialNumber=DN044EHJ,mConfigurations=[\nUsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=45,mInterfaces=[\nUsbInterface[mId=0,mAlternateSetting=0,mName=FT230X Basic UART,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 -1;-1;0 Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. done showing download page checkPendingIntents Column width 411 root item width 411 width in Grid Units 27 original gridUnit 15 now 15 Using the following font: Roboto at 12pt with mobile_scale: 1 qqwindow devicePixelRatio 3.50092 3.50092 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), i200C (SERIAL, BLE), i300 (SERIAL), i300C (SERIAL, BLE), i450T (SERIAL), i550 (SERIAL), i550C (SERIAL, BLE), i750TC (SERIAL, BT), i770R (SERIAL, BLE)" "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: Cartesio (SERIAL), Drake (SERIAL), Giotto (SERIAL), Goa (SERIAL), Leonardo (SERIAL), Newton (SERIAL)" "Deepblu: Cosmiq+ (BLE)" "DiveSystem: Orca (SERIAL), iDive DAN (SERIAL), iDive Deep (SERIAL), iDive Easy (SERIAL), iDive Free (SERIAL), iDive Pro (SERIAL), iDive Reb (SERIAL), iDive Stealth (SERIAL), iDive Tech (SERIAL), iDive X3M (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: Genius (SERIAL, BLE), Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE), Smart Air (SERIAL, BLE), Smart Apnea (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), Geo 4.0 (SERIAL, BLE), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2
Re: Ratio ix3m Pro on Android
Finally back at home and was able to test with my one and only partially functional FTDI dive computer. It turns out this is a bug in the current sources where it shows the wrong error code. This is an indication that you have one of the majority of Android devices that don't support the current way in which we try to access FTDI devices. /D > On Sep 13, 2019, at 4:24 AM, liquid tcp wrote: > > > Could you try to download again and then go to the "About" page and copy > > the log files and paste them into an email? > > From the below it seems that Subsurface-mobile is running out of memory - > > which is very surprising to me. Yes, it is a bit of a memory hog, bit even > > on fairly old devices running out of memory is extremely rare... > > /D > > sure, here are the logs. just did, to be sure, a reboot and cleaned the > memory, so I'm having 2.5GB available with subsurface using 193MB giving me > the same behaviour. here the full logs: > > -- subsurface.log -- > "0.003: Failed to open logfile /storage/emulated/0/subsurface.log at Fri Sep > 13 13:12:44 2019 error: Permission denied" > "0.004: Failed to open logfile /storage/emulated/0/Documents/subsurface.log > at Fri Sep 13 13:12:44 2019 error: Permission denied" > "0.004: Successfully opened logfile > /storage/emulated/0/Android/data/org.subsurfacedivelog.mobile/files/Documents/subsurface.log > at Fri Sep 13 13:12:44 2019" > "0.004: Starting Subsurface-mobile:2.2.0(4.9.3.16):Android (9.0):arm64:en-US" > "0.004: built with libdivecomputer v0.7.0-devel-Subsurface-NG > (ce6d9896a79afaa82641132e338f8744714c8593)" > "0.004: built with Qt Version 5.12.4, runtime from Qt Version 5.12.4" > "0.004: built with libgit2 0.26.0" > BTDiscoveryReDiscover: localBtDevice.isValid() true > localBtDevice isn't valid or not connectable > "Created position source android" > "0.014: Created position source android" > "Set GPS service update interval to 300 s" > "0.015: Set GPS service update interval to 300 s" > "0.015: location service is not available" > qrc:/org/kde/kirigami/Page.qml:276:5: QML Loader: Binding loop detected for > property "active" > QQmlExpression: Expression qrc:/qml/DownloadFromDiveComputer.qml:338:5 > depends on non-NOTIFYable properties: > QMLManager::DC_forceDownload > Model size of -1 is less than 0 > Both point size and pixel size set. Using pixel size. > "0.578: Synchronising data file" > "0.584: Load dives from local cache" > "0.587: Successfully opened dive data" > "0.588: 7 dives loaded from cache" > "0.589: have cloud credentials, but user asked not to connect to network" > "1.096: > UsbDevice[mName=/dev/bus/usb/001/002,mVendorId=1027,mProductId=24597,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=FTDI,mProductName=FT230X > Basic > UART,mVersion=10.00,mSerialNumber=DN044EHJ,mConfigurations=[\nUsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=45,mInterfaces=[\nUsbInterface[mId=0,mAlternateSetting=0,mName=FT230X > Basic > UART,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 -1;-1;0 > Both point size and pixel size set. Using pixel size. > Both point size and pixel size set. Using pixel size. > done showing download page > checkPendingIntents > Column width 411 root item width 411 > width in Grid Units 27 original gridUnit 15 now 15 > Using the following font: Roboto at 12pt with mobile_scale: 1 > qqwindow devicePixelRatio 3.50092 3.50092 > 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), i200C (SERIAL, BLE), i300 (SERIAL), i300C (SERIAL, > BLE), i450T (SERIAL), i550 (SERIAL), i550C (SERIAL, BLE), i750TC (SERIAL, > BT), i770R (SERIAL, BLE)" > "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: Cartesio (SERIAL), Drake (SERIAL), Giotto (SERIAL), Goa (SERIAL), > Leonardo (SERIAL), Newton (SERIAL)" > "Deepblu: Cosmiq+ (BLE)" > "DiveSystem: Orca (SERIAL), iDive DAN (SERIAL), iDive Deep (SERIAL), iDive > Easy (SERIAL), iDive Free (SERIAL), iDive Pro (SERIAL), iDive Reb (SERIAL), > iDive Stealth (SERIAL), iDive Tech (SERIAL), iDive X3M (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
