[BRLTTY] mantis q40

[Florian Beijers]

Just realized I only sent this to Mario before, my bad.
I have done some more experimenting, and quite simply, the unit just
won't sit up and take notice where brltty is concerned. Connection
goes off without a hitch, the HID keyboard part works, but error 111:
connection refused from RFCOMM is all the logs show.
I've tried connecting through the GUI as well as bluetoothctl,
manually trusting the device first, re-paring it several times without
result.
So I guess this is when I have to conclude there's a bug :) I just
looked at the github repo but I don't see the issues tab being there.
What is the procedure for submitting a bug report?

Thanks,
Florian

2021-02-09 20:59 GMT+01:00, Florian Beijers <florianbeijers at gmail.com>:
> Ok, I ran a few more tests but still am not really getting anywhere.
>
> I tailed the journalctl to see what wold happen if I were to cycle to and
> away from the box I'm trying to connect, that did nothing whatsoever.
> Then, I hopped back into bluetoothctl and saw that it was connecting and
> disconnecting repeatedly every few seconds.
> I deleted the device, re-paired it and explicitly gave the connect command,
> that made it stop flickering.
> Tailing the journalctl again I now see L2CAP: connection timed out, as well
> as "software caused connection abort" errors in the logs. Does that help
> with diagnosing what's happening?
>
>
>
> Op di 9 feb. 2021 om 19:57 schreef Florian Beijers
> <florianbeijers at gmail.com
>>:
>
>> Hi,
>>
>> Ok, so the mantis q40 is a hybrid device of a keyboard and a braille
>> display. I have paired it through the GUI and I can confirm that the
>> keyboard part of it works fine. So I would say it is paired correctly.
>> The way this device works is that you can connect to several devices at
>> once, with a little menu that cycles in between devices.
>> I currently am not near the device but when I was logging, I didn't have
>> the device's channel selected, which lead to the "connection refused"
>> log.
>> My theory, which I haven't been able to validate yet, is that "resource
>> busy" comes up when either one of the other channels is in use, or when
>> I'm
>> actually connected to the device, in which case the driver or the device
>> internals are doing something weird. I'll report back when I have all the
>> permutations logged.
>>
>> Florian
>>
>> Op di 9 feb. 2021 om 19:45 schreef Mario Lang <mlang at blind.guru>:
>>
>>> Florian Beijers <florianbeijers at gmail.com> writes:
>>>
>>> > I see a whole lot of RFCOMM errors, either connection refused or
>>> resource busy.
>>> > What would that indicate?
>>>
>>> My first question would be: Are you sure you have correctly paired the
>>> device?  Does bluetoothctl report it as paired?
>>>
>>> --
>>> CYa,
>>>   ⡍⠁⠗⠊⠕
>>>
>>
>