On 11 June, 2018 - Jef Driesen wrote:
> On 11-06-18 20:21, Anton Lundin wrote:
> >On 04 June, 2018 - Dirk Hohndel wrote:
> >
> >>I don't have an outstanding patch from you, so not sure what you are
> >>referring to.
> >
> >There was a diff a while back in this thread, in
>
On Montag, 11. Juni 2018 20:50:56 CEST Linus Torvalds wrote:
> BLE is kind of odd. We also do things kind of oddly, because the way
> we generate that 16-bit value is with
>
> QByteArray::fromHex("0100")
I think the idiomatic way to do this is the
QByteArrayLiteral("\x01\x00")
macro
On Mon, 11 Jun 2018 at 20:21, Anton Lundin wrote:
>
> On 04 June, 2018 - Dirk Hohndel wrote:
>
> > I don't have an outstanding patch from you, so not sure what you are
> > referring to.
>
> There was a diff a while back in this thread, in
> 20180523144751.gc12...@hirohito.acc.umu.se , which made
On 11-06-18 20:21, Anton Lundin wrote:
On 04 June, 2018 - Dirk Hohndel wrote:
I don't have an outstanding patch from you, so not sure what you are referring
to.
There was a diff a while back in this thread, in
20180523144751.gc12...@hirohito.acc.umu.se , which made the code fall
back to the
On 11 June 2018 at 21:50, Linus Torvalds wrote:
> On Mon, Jun 11, 2018 at 11:31 AM Lubomir I. Ivanov
> wrote:
>>
>> the Qt BLE Windows stack on the other hand detects it as "Write
>> without response".
>> this has to be investigated - possible bug.
>
> That's how you enable notifications - you
On Mon, Jun 11, 2018 at 11:31 AM Lubomir I. Ivanov wrote:
>
> the Qt BLE Windows stack on the other hand detects it as "Write
> without response".
> this has to be investigated - possible bug.
That's how you enable notifications - you write a 16-bit value to the
notification thing that has the
On 11 June 2018 at 20:36, Jan Mulder wrote:
> On 11-06-18 19:20, Lubomir I. Ivanov wrote:
>>
>> On 11 June 2018 at 20:00, Jan Mulder wrote:
>>> Check for the correct ready byte is not done at the Subsurface side, but
>>> in
>>> the libdivecomputer procedure hw_ostc3_transfer(...). But not sure
On 08 June, 2018 - C. Hoefer wrote:
> Hello,
>
> I'm trying to start using subsurface mobile.
>
> Is there a tool to convert my xml logbook to the format used with the
> mobile? Back and forth at best. :-)
The simple answer is Use the cloud service. Its the only supported
source for subsurface
On 04 June, 2018 - Dirk Hohndel wrote:
> I don't have an outstanding patch from you, so not sure what you are
> referring to.
There was a diff a while back in this thread, in
20180523144751.gc12...@hirohito.acc.umu.se , which made the code fall
back to the voted/averaged ppo2 instead of
On 11 June, 2018 - Lubomir I. Ivanov wrote:
> On 11 June 2018 at 20:00, Jan Mulder wrote:
> > On 11-06-18 18:29, Lubomir I. Ivanov wrote:
> >>
> >> On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
> >>>
> >>> On 11 June 2018 at 17:49, Dirk Hohndel wrote:
>
>
> > On Jun 10,
On 11-06-18 19:20, Lubomir I. Ivanov wrote:
On 11 June 2018 at 20:00, Jan Mulder wrote:
On 11-06-18 18:29, Lubomir I. Ivanov wrote:
On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
On 11 June 2018 at 17:49, Dirk Hohndel wrote:
On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov
wrote:
On 11 June 2018 at 20:00, Jan Mulder wrote:
> On 11-06-18 18:29, Lubomir I. Ivanov wrote:
>>
>> On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
>>>
>>> On 11 June 2018 at 17:49, Dirk Hohndel wrote:
> On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov
> wrote:
>
> 2) so
On 11-06-18 18:29, Lubomir I. Ivanov wrote:
On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
On 11 June 2018 at 17:49, Dirk Hohndel wrote:
On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov wrote:
2) so OSTC+ has a certain service with 4 WriteNoResponse
characteristics (no READ,
On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
> On 11 June 2018 at 17:49, Dirk Hohndel wrote:
>>
>>> On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov wrote:
>>>
>>> 2) so OSTC+ has a certain service with 4 WriteNoResponse
>>> characteristics (no READ, WRITE-ONLY) which is supposedly the
On 11-06-18 17:16, Lubomir I. Ivanov wrote:
This code was written based on documentation of the BLE stack that the
OSTC implements.
I wonder if the four characteristics are in the same order. It would be
interesting
to dump all the information we can get on the four of them both under Windows
> On Jun 11, 2018, at 8:16 AM, Lubomir I. Ivanov wrote:
>>> 2) so OSTC+ has a certain service with 4 WriteNoResponse
>>> characteristics (no READ, WRITE-ONLY) which is supposedly the service
>>> we have to use for communicating to the device. at least we assume
>>> that in Subsurface but i don't
On 11 June 2018 at 18:16, Lubomir I. Ivanov wrote:
> On 11 June 2018 at 17:49, Dirk Hohndel wrote:
>>
>>> On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov wrote:
>>>
>>> On 10 June 2018 at 16:04, Lubomir I. Ivanov wrote:
BT classical mode works - i was able to download 10 dives, that
On 11 June 2018 at 17:49, Dirk Hohndel wrote:
>
>> On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov wrote:
>>
>> On 10 June 2018 at 16:04, Lubomir I. Ivanov wrote:
>>>
>>> BT classical mode works - i was able to download 10 dives, that
>>> apparently already existed on the DC.
>>> i need to debug
> On Jun 11, 2018, at 7:44 AM, Lubomir I. Ivanov wrote:
Your debug log doesn't actually have the IO that is done. That seems
to be a Qt issue. We ask for debug output, and some versions of Qt
will give that:
> On Jun 10, 2018, at 5:36 PM, Lubomir I. Ivanov wrote:
>
> On 10 June 2018 at 16:04, Lubomir I. Ivanov wrote:
>>
>> BT classical mode works - i was able to download 10 dives, that
>> apparently already existed on the DC.
>> i need to debug the BLE response from the device.
>>
>
> status
On 11 June 2018 at 17:40, Dirk Hohndel wrote:
>
>> On Jun 11, 2018, at 4:47 AM, Thiago Macieira wrote:
>>
>> On Sunday, 10 June 2018 01:59:37 CEST Linus Torvalds wrote:
>>> Your debug log doesn't actually have the IO that is done. That seems
>>> to be a Qt issue. We ask for debug output, and
> On Jun 11, 2018, at 4:47 AM, Thiago Macieira wrote:
>
> On Sunday, 10 June 2018 01:59:37 CEST Linus Torvalds wrote:
>> Your debug log doesn't actually have the IO that is done. That seems
>> to be a Qt issue. We ask for debug output, and some versions of Qt
>> will give that:
>>
>>
> On Jun 11, 2018, at 6:52 AM, Jan Mulder wrote:
>
> On 11-06-18 15:18, Jan Mulder wrote:
>
>> I will try to fire up my Windows machine, to check what is happing there
>> in BLE context (but disclaimer: I'm far from a Windows developer).
>
> Tried the Windows BLE build on Windows 8.1.
On 11 June 2018 at 16:52, Jan Mulder wrote:
> On 11-06-18 15:18, Jan Mulder wrote:
>
>>
>> I will try to fire up my Windows machine, to check what is happing there
>> in BLE context (but disclaimer: I'm far from a Windows developer).
>
>
> Tried the Windows BLE build on Windows 8.1. OSTC3
On 11-06-18 15:18, Jan Mulder wrote:
I will try to fire up my Windows machine, to check what is happing there
in BLE context (but disclaimer: I'm far from a Windows developer).
Tried the Windows BLE build on Windows 8.1. OSTC3 correctly paired on OS
level. Download over BT does work
> On 10 June 2018 at 16:04, Lubomir I. Ivanov wrote:
>>
>> BT classical mode works - i was able to download 10 dives, that
>> apparently already existed on the DC.
>> i need to debug the BLE response from the device.
>>
>
> status report:
> so sadly i'm observing a multitude of problems here
On Sunday, 10 June 2018 01:59:37 CEST Linus Torvalds wrote:
> Your debug log doesn't actually have the IO that is done. That seems
> to be a Qt issue. We ask for debug output, and some versions of Qt
> will give that:
>
> QLoggingCategory::setFilterRules(QStringLiteral("qt.bluetooth*
> =
27 matches
Mail list logo
