<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yes, you are missing that Android is taking away access to things that look like storage from regular apps.<div class="">You can access pictures and media files, but you can no longer just read storage... Well, in Android 10 you still can, in 11 this will go away.</div><div class=""><br class=""></div><div class=""><a href="https://developer.android.com/preview/privacy/storage" class="">https://developer.android.com/preview/privacy/storage</a></div><div class=""><br class=""></div><div class="">Because of that, I haven't bothered to implement this.</div><div class=""><br class=""></div><div class="">/D<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 9, 2020, at 4:40 PM, Miika Turkia via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div dir="ltr" class="">I should be able to run logcat once I have collected more test data. I just need to figure out how to do that over wifi or BT. Have always connected with usb cable before, but that is not an option this time :)</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">BTW I just realized that Garmin is not supported, but it should probably be relatively easy to add. It is mounted as a disk and we need to just point to right mount point. Or am I missing something?</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On 10. Mar 2020, at 6.45, Christof Arnosti <<a href="mailto:charno@charno.ch" class="">charno@charno.ch</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class=""><p class="">Hi,</p><p class="">Thanks. The Info (idVendor / idProduct) is already in the log you
sent, so no need to download the app.<br class="">
</p><p class="">I want to get some (more or less) statistical data about which
usb-to-serial chipset behaves how. This is a big help! :)</p><p class="">If you have some experience in the android world, could you maybe
try to run "adb logcat" while downloading the dives? The logcat
output might help with pinpointing the application crash, and I
think until now yours is the only report of an actual application
crash.<br class="">
</p><p class="">Best regards<br class="">
Christof</p>
<div class="moz-cite-prefix">Am 09.03.20 um 23:39 schrieb Miika
Turkia:<br class="">
</div>
<blockquote type="cite" cite="mid:CAEB307Pj3q0NBFCeSeX0XMWOA-XnScmv9aPMC+tpS7we5sCKiQ@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 10, 2020 at 6:32
AM Christof Arnosti via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" moz-do-not-send="true" class="">subsurface@subsurface-divelog.org</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class=""><p class="">Thanks for the more in-depth ;-) test.</p><p class="">Having a look at the serial-interface chipset-list at <a href="http://libdivecomputer.org/drivers.html" target="_blank" moz-do-not-send="true" class="">http://libdivecomputer.org/drivers.html</a>
I noticed that suunto uses two different chipsets. Maybe
this could be a lead to follow up? <br class="">
</p><p class="">Can the people owning a suunto computer maybe post the
Vendor ID / Product ID of their cable, and if it works
or not? The App
<a href="https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator" target="_blank" moz-do-not-send="true" class="">https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator</a>
shows these values.<br class="">
</p>
</div>
</blockquote>
<div class="">This is what I get on dmesg when attaching the D4 cable:</div>
<div class="">---8<---<br class="">
</div>
<div class="">[30804.146977] usb 1-2: new full-speed USB device number
12 using xhci_hcd<br class="">
[30804.301648] usb 1-2: New USB device found, idVendor=0403,
idProduct=6001<br class="">
[30804.301653] usb 1-2: New USB device strings: Mfr=1,
Product=2, SerialNumber=0<br class="">
[30804.301657] usb 1-2: Product: USB <-> Serial Cable<br class="">
[30804.301660] usb 1-2: Manufacturer: Smartinterface<br class="">
[30804.890118] usbcore: registered new interface driver
ftdi_sio<br class="">
[30804.890187] usbserial: USB Serial support registered for
FTDI USB Serial Device<br class="">
[30804.890504] ftdi_sio 1-2:1.0: FTDI USB Serial Device
converter detected<br class="">
[30804.890728] usb 1-2: Detected FT232RL<br class="">
[30804.891105] usb 1-2: FTDI USB Serial Device converter now
attached to ttyUSB0</div>
<div class="">---8<---</div>
<div class=""><br class="">
</div>
<div class="">Downloading from D4 with this cable on Android 7.1.1, the
Subsurface crashes after about 4 dives. Do you think the OTG
cable plays a part on this? I can try the app you mention if
that would be beneficial.</div>
<div class=""><br class="">
</div>
<div class="">miika<br class="">
</div>
</div>
</div>
</blockquote>
</div></blockquote></div>_______________________________________________<br class="">subsurface mailing list<br class=""><a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a><br class="">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface<br class=""></div></blockquote></div><br class=""></div></body></html>