Thanks, Claudiu... this is looking promising.
Thanks for the great news, Dirk.
Now we need to figure out what's going on on Mac.
I am not sure how I can help you with this. I don't have a
Mac device. I could try to install OSx on a virtual machine.
Or I could start to investigate the
On Wed, Jul 08, 2015 at 11:47:18AM +0300, Claudiu Olteanu wrote:
Now we need to figure out what's going on on Mac.
I am not sure how I can help you with this. I don't have a
Mac device. I could try to install OSx on a virtual machine.
That is unlikely to help. Mac VM support is extremely
I managed to compile the project with Qt5.5.0. I saw that Bluetooth
connectivity
doesn't work for the moment with this version. I will investigate it
tomorrow.
I just wanted to let you know that I managed to successfully download
the dives from both devices using our custom BT serial
The only way you're allowed to run OS X in a VM is if you have genuine
Apple
hardware, which usually implies you've already got access to OS X in real
hardware anyway...
I didn't know that. Thanks for the info!
Is it ok with you if I start the documentation for the second stage of the
On Wednesday 08 July 2015 11:47:18 Claudiu Olteanu wrote:
I am not sure how I can help you with this. I don't have a
Mac device. I could try to install OSx on a virtual machine.
The only way you're allowed to run OS X in a VM is if you have genuine Apple
hardware, which usually implies you've
On Monday 06 July 2015 22:03:52 Dirk Hohndel wrote:
I tried testing on Ubuntu, also in a VM on the same Mac. But I can't seem
to figure out which package to install to get the QtBluetooth stuff. Any
suggestion on the right package names? This needs to be added to the
INSTALL file, too...
It
On Mon, Jul 06, 2015 at 10:17:12PM -0700, Dirk Hohndel wrote:
My guess is that this is because I'm in a VM. Once I figure out the Ubuntu
situation I'll use a different computer that is running Ubuntu directly. I
don't consider being able to run inside a VM critical...
And I was able to verify
On Tue, Jul 7, 2015 at 9:02 AM, Thiago Macieira thi...@macieira.org wrote:
On Monday 06 July 2015 22:03:52 Dirk Hohndel wrote:
I tried testing on Ubuntu, also in a VM on the same Mac. But I can't seem
to figure out which package to install to get the QtBluetooth stuff. Any
suggestion on the
On Tue, Jul 07, 2015 at 01:49:08PM +0300, Miika Turkia wrote:
On Tue, Jul 7, 2015 at 9:02 AM, Thiago Macieira thi...@macieira.org wrote:
On Monday 06 July 2015 22:03:52 Dirk Hohndel wrote:
I tried testing on Ubuntu, also in a VM on the same Mac. But I can't seem
to figure out which package
When I manage to connect to the OSTC 2 device and to initiate the data
transfer I get the same result. It gets stuck somewhere in the middle.
The libdivecomputer back-end initiate a read request for a 1024 buffer
and can read only 923 bytes from device's buffer.
I will let you know if the new
Hi,
I wanted to let you know that after I did the firmware upgrade everything
works fine. I tested both devices on all three environments
(OpenSuse, Fedora, ArchLinux) and I didn't encounter any problem.
Now we just have to figure out why Dirk's devices don't work.
Dirk, do you have other
On Monday 06 July 2015 23:00:08 Claudiu Olteanu wrote:
Thiago, do you have a dive computer with Bluetooth support? Do you
believe that you can help me with some tests?
No, I don't have one. I could probably borrow one from Dirk, but please don't
expect a lot of availability to do debugging...
Sorry, my mistake! Somehow I deleted the qtserialbluetooth.cpp source
from SUBSURFACE_CORE_LIB_SRCS list :-).
I managed to compile the project with Qt5.5.0. I saw that Bluetooth
connectivity
doesn't work for the moment with this version. I will investigate it
tomorrow.
On Monday 06 July 2015 21:41:37 Claudiu Olteanu wrote:
libsubsurface_corelib.a(libdivecomputer.c.o): In function
`do_libdivecomputer_import':
/home/claudiu/gsoc/subsurface/libdivecomputer.c:930: undefined reference to
`dc_serial_qt_open'
The method is declared as external C and is
On Mon, Jul 06, 2015 at 11:00:08PM +0300, Claudiu Olteanu wrote:
Hi,
I wanted to let you know that after I did the firmware upgrade everything
works fine. I tested both devices on all three environments
(OpenSuse, Fedora, ArchLinux) and I didn't encounter any problem.
Now we just have to
On Mon, Jul 06, 2015 at 11:00:08PM +0300, Claudiu Olteanu wrote:
Hi,
I wanted to let you know that after I did the firmware upgrade everything
works fine. I tested both devices on all three environments
(OpenSuse, Fedora, ArchLinux) and I didn't encounter any problem.
Now we just have to
On Mon, Jul 06, 2015 at 10:03:52PM -0700, Dirk Hohndel wrote:
On Mon, Jul 06, 2015 at 11:00:08PM +0300, Claudiu Olteanu wrote:
Hi,
I wanted to let you know that after I did the firmware upgrade everything
works fine. I tested both devices on all three environments
(OpenSuse, Fedora,
Hi there,
I spent this week doing some tests to find out the possible reasons
of some issues:
- first the QtSocketBluetooth::connectToService(address, uuid, mode)
doesn't work as expected. On some devices, the SPP profile is never found.
- second on some environments the connection takes too
I forgot to specify that the Fedora 22 and ArchLinux environments
are two virtual machines. I don't know if this could cause the problem.
If it does, I expect that it shouldn't work with the HW OSTCs device as
well.
Claudiu
___
subsurface mailing list
On Sun, Jul 05, 2015 at 10:50:59PM +0300, Claudiu Olteanu wrote:
Hi there,
I spent this week doing some tests to find out the possible reasons
of some issues:
- first the QtSocketBluetooth::connectToService(address, uuid, mode)
doesn't work as expected. On some devices, the SPP profile is
20 matches
Mail list logo
