Android beta... - FTDI download

[Werner Macho]

Hi,

It seems that being "a quiet, non-coding, time-limited
reader of your mailing list" is unfortunately also true for me.

But I also want to share my current experience.

Some weeks ago I was able to download from my OSTC sport to my Oneplus X
with lineageOS.

Now this has unfortunately changed.

Installed is latest LineageOS 14.1 from 6.July 2017
OSTC sport is latest firmware v10.37

bluetooth is paired but there is no connection with download.


>From what I can see in the log.
2.0(4.6.4.380): Android Nougat (7.1): arm:en-GB""0.002: build with Qt
Version 5.9.1, runtime from Qt Version 5.9.1"
localBtDevice isn't valid
...
...
"22.847: DCDownloadThread started for cannot determine address of dive
computer"
Starting download from BT
Starting the thread 0
connecting to Uui
"{00001101-000-1000-8000-00805f9b34fb}"
connectToService() "00:00:00:00:00:00"
"00001101-000-1000-8000-00805f9b34fb}"
Bt device offline
Failed to connect to device cannot determine address if dive computer .
Device state QBluetoothSocket::UnconnectedState .
Error:QBluetoothSocket::NetworkError
Finishing the thread Insufficient privileges to open the device %s %s (%s)
dives downloaded 0 no new dives downloaded.
...
...

I realised that bluetooth is still off. Is there a way to activate
bluetooth automatically when the bluetooth checkbox is checked?

After activating bluetooth the lines from "Bt device offline" downwards
changed to:

Connnecting via insecure rfcomm
Connecting socket
The connection step took more than expected.
Wait another 20 seconds
Falling back to reverse uuid workaround.
Workaround failed
Failed to connect ........ same as above

I afterwards also checked with my backup mobile (no custom firmware - just
plain old Android 4.4.2) to make sure it is not a mobile or Android problem.
The same results.

I am also a DiveMate user and the download there is working (if that helps
in any way).

Thanks a lot for creating subsurface. I use it to archive all my dives.
If only I could help more - coding skills are very limited, unfortunately.

regards
Werner


On Mon, Jul 10, 2017 at 12:04 AM, Dirk Hohndel <dirk at hohndel.org> wrote:

>
> > On Jul 9, 2017, at 3:02 PM, Dietrich Meyer <dietrich at sunnynames.com>
> wrote:
> >
> > On Sonntag, 9. Juli 2017 23:53:36 CEST you wrote:
> >>> but with your help I see the problem:
> >>> there is a line
> >>> "Finished thread Insufficient privileges to open the device %s %s (%s)
> >>> dives downloaded 0"
> >>> next line reads
> >>> "50.409: DCDownloadThread finished"
> >>>
> >>> So some privileges problem..... probably similar to what was discussed
> >>> previously with selinux....
> >>
> >> Actually, that's another potentially painfully misleading error message.
> >> Is there anything useful in the lines just before this?
> >
> > There are three more lines:
> > -----------------------------------------------------
> > "50.393: DCDownloadThread started for /tmp/ttyS1"
> > Starting download from   ftdi
> > Starting the thread 0
> > ---------------------------------------
> >
> > This seems ok. Everything above that and below the "50.409:
> DCDownloadThread
> > finished" is not related to download (pixel size etc).
>
>
> Correct analysis. I'm about NN minutes away from an update that provides
> much better debug information. I hope NN < 30 - but I have learned not to
> make such promises.
>
> /D
> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20170710/fea72db2/attachment-0001.html>