[BRLTTY] Brltty beep on android

[payman shaykhmehdi]

>
> Now to your beep issue. I think it's caused by this:
>
>    unhandled command: 00FF
>
> Brltty does beep when it receives a command from the braille driver that it
> doesn't recognize.


Is there any difference between command handlers in Android and linux?
Because with the same driver I don't receive "unhandled command" warning.
Also in my driver I just send key press/release events.

On Thu, Jul 19, 2018 at 12:52 PM, Dave Mielke <Dave at mielke.cc> wrote:

> It looks like you aren't using the latest brltty apk. That may mean that
> many
> problems have been resolved since the one you're using. Perhaps you should
> upgrade.
>
>
>
> You're getting this log once in a while:
>
>    checkTalkbackEnable : false, accesibilityService :
> org.a11y.brltty.android/org.a11y.brltty.android.BrailleService
>
> While it's harmless enough, brltty, at least for now, works better when
> TalkBack is enabled. The reason is that brltty uses the Accessibility Focus
> feature, which, unfortunately, isn't implemented as a standalone
> capability.
> It's part of Explore By Touch, which, in turn, is paty of TalkBack.
>
> I know of one user who has solved this problem by installing a null TTS.
> So,
> even though TalkBack is active, nothing is spoken. I forget it's exact
> name at
> the moment, but searching the store for something like null tts should
> find it.
>
> The first part of your log contains these logs:
>
>    malloc error 11: Try again.
>    malloc error 5: I/O error.
>
> Whenever either of these occurs, it's imediately followed by this one:
>
>    Bluetooth connect failed: B8:27:EB:BB:3C:85: Bluetooth is off
>
> When Bluetooth is finally on, you get this pair of logs:
>
>    Bluetooth connect failed: B8:27:EB:BB:3C:85: bt socket connect failed
>    Bluetooth connect failed: B8:27:EB:BB:3C:85: read failed, socket might
> closed or timeout, read ret: -1
>
> These are okay. They just mean that brltty couldn't connect to the braille
> device. The Java Exception for this case isn't specific enough for brltty
> to
> know the precise cause of the connection failure.
>
> Now to your beep issue. I think it's caused by this:
>
>    unhandled command: 00FF
>
> Brltty does beep when it receives a command from the braille driver that it
> doesn't recognize.
>
> You're also getting these:
>
>    Unexpected Packet: 04 00 80 00 FF 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10
> 11 12 13 14 15 16 17 18 0B 1A 1B 1C 1D 20 82
>
> Since I believe this is your own protocol, I'm not sure how significant
> they
> are.
>
> --
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20180722/01a08568/attachment.html>