<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Now to your beep issue. I think it's caused by this:<br>
<br>
unhandled command: 00FF<br>
<br>
Brltty does beep when it receives a command from the braille driver that it<br>
doesn't recognize.</blockquote><div><br></div><div>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. <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 19, 2018 at 12:52 PM, Dave Mielke <span dir="ltr"><<a href="mailto:Dave@mielke.cc" target="_blank">Dave@mielke.cc</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It looks like you aren't using the latest brltty apk. That may mean that many<br>
problems have been resolved since the one you're using. Perhaps you should<br>
upgrade.<br>
<br>
<br>
<br>
You're getting this log once in a while:<br>
<br>
checkTalkbackEnable : false, accesibilityService : org.a11y.brltty.android/org.<wbr>a11y.brltty.android.<wbr>BrailleService<br>
<br>
While it's harmless enough, brltty, at least for now, works better when<br>
TalkBack is enabled. The reason is that brltty uses the Accessibility Focus<br>
feature, which, unfortunately, isn't implemented as a standalone capability.<br>
It's part of Explore By Touch, which, in turn, is paty of TalkBack.<br>
<br>
I know of one user who has solved this problem by installing a null TTS. So,<br>
even though TalkBack is active, nothing is spoken. I forget it's exact name at<br>
the moment, but searching the store for something like null tts should find it.<br>
<br>
The first part of your log contains these logs:<br>
<br>
malloc error 11: Try again.<br>
malloc error 5: I/O error.<br>
<br>
Whenever either of these occurs, it's imediately followed by this one:<br>
<br>
Bluetooth connect failed: B8:27:EB:BB:3C:85: Bluetooth is off<br>
<br>
When Bluetooth is finally on, you get this pair of logs:<br>
<br>
Bluetooth connect failed: B8:27:EB:BB:3C:85: bt socket connect failed<br>
Bluetooth connect failed: B8:27:EB:BB:3C:85: read failed, socket might closed or timeout, read ret: -1<br>
<br>
These are okay. They just mean that brltty couldn't connect to the braille<br>
device. The Java Exception for this case isn't specific enough for brltty to<br>
know the precise cause of the connection failure.<br>
<br>
Now to your beep issue. I think it's caused by this:<br>
<br>
unhandled command: 00FF<br>
<br>
Brltty does beep when it receives a command from the braille driver that it<br>
doesn't recognize.<br>
<br>
You're also getting these:<br>
<br>
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<br>
<br>
Since I believe this is your own protocol, I'm not sure how significant they<br>
are.<br>
<div class="HOEnZb"><div class="h5"><br>
-- <br>
I believe the Bible to be the very Word of God: <a href="http://Mielke.cc/bible/" rel="noreferrer" target="_blank">http://Mielke.cc/bible/</a><br>
Dave Mielke | 2213 Fox Crescent | WebHome: <a href="http://Mielke.cc/" rel="noreferrer" target="_blank">http://Mielke.cc/</a><br>
EMail: Dave@Mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke<br>
Phone: +1 613 726 0014 | Canada K2A 1H7 |<br>
______________________________<wbr>_________________<br>
This message was sent via the BRLTTY mailing list.<br>
To post a message, send an e-mail to: BRLTTY@brltty.app<br>
For general information, go to: <a href="http://brltty.app/mailman/listinfo/brltty" rel="noreferrer" target="_blank">http://brltty.app/mailman/<wbr>listinfo/brltty</a><br>
</div></div></blockquote></div><br></div>