Testing ftdi code

[Willem Ferguson]

On 11/10/2016 14:18, Anton Lundin wrote:
>> On 18/09/2016 10:48, Anton Lundin wrote:
>>> After the last round of custom serial rewrite, the ftdi custom serial
>>> code now can be used with all libdivecomputer backends, and not just
>>> OSTC3.
>>>
>>> 3. Plug in your ftdi device/cable and chown the usb character device
>>> your test user. lsusb will give you bus / device and the device is found
>>> at /dev/bus/usb/$bus/$device . This can be automated with udev.
>>>
>>>
>>> //Anton
>>>
Anton,

Seems to work ok on my Ubuntu with Tusa IQ900 (equiv of Oceanic Atom2)

One error message close to the beginning:
INFO: Flush: queue=3, input=0, output=-1
INFO: Wrote 2 bytes
INFO: Read 1 bytes
INFO: Read 17 bytes
INFO: Wrote 4 bytes
INFO: Sleep: value=1
INFO: Sleep: value=2
INFO: Sleep: value=4
INFO: Sleep: value=8
INFO: Sleep: value=16
INFO: Sleep: value=32
INFO: Sleep: value=64
INFO: Sleep: value=128
INFO: Sleep: value=256
INFO: Sleep: value=489
ERROR: FTDI read timed out.
[1.917694] ERROR: Failed to receive the answer. [in 
../../src/oceanic_atom2.c:473 (oceanic_atom2_packet)]
INFO: Flush: queue=1, input=0, output=-1
INFO: Wrote 4 bytes
INFO: Sleep: value=1

Dives load ok into memory and display ok within Subsurface, though.

Next step: run on Android.
1) Download appropriate Android ftdi lib.
2) Compile desktop to Android. Using which options? Where? Does it 
produce an .apk?

Kind regards,
willem