[BRLTTY] brltty for Android

[Rasmussen, Lloyd]

In the case of BARD Mobile, it may not be easy for anyone to fix this in BrlTTY. We are using controls with nonstandard behavior for fast forward, rewind, next and previous in our BARD Mobile app. Double-tap activates the button for a one-time action, while tap and hold holds the button down until released, which is not standard Android behavior for the tap-and-hold gesture. We have this working properly in TalkBack and with no access technology running, but it doesn’t work in BrailleBack, either.

Lloyd Rasmussen, Senior Staff Engineer
National Library Service for the Blind and Physically Handicapped, Library of Congress
Washington, DC 20542   202-707-0535
http://www.loc.gov/nls/
The preceding opinions are my own and do not necessarily reflect those of the Library of Congress, NLS.

From: brltty-bounces at mielke.cc [mailto:brltty-bounces at mielke.cc] On Behalf Of Devin Prater
Sent: Wednesday, December 14, 2016 12:25 AM
To: Informal discussion between users and developers of BRLTTY.
Subject: Re: [BRLTTY] brltty for Android

Oh, okay. The bug I was having also appears in the (recycler view) apps, like Facebook. Thanks for letting users see stuff like that, too. Another problem I'm having which may be brltty related, but may be a problem with the app, is that I cannot activate some buttons in the BARD Mobile app, like previous or next navigation setting, but play/stop works fine.

On Tue, Dec 13, 2016 at 10:26 PM Dave Mielke <dave at mielke.cc> wrote:
[quoted lines by Devin Prater on 2016/12/14 at 03:14 +0000]

>I have Brltty 5.4.apk, from the brltty download page.

You probably want the latest apk, then, as it fixes an annoying problem that
I'm sure you're having. When adding to the end of an input area, the braille
cursor would jump back to the beginning after typing a space. The real cursor
was still in the right place, of course, to further characters still did get
added to the end of the input area, and the braille cursor would go back to the
right place as soon as a non-space was entered. The problem, ion other words,
was that the braille cursor was placed at the start of an input area if the
real cursor was on a space at the end of that input area.

To get the latest apk: go to brltty.com<http://brltty.com>, click on Download, and then on
Android.

>No, sorry, I don't know how to capture logs.

Do you have the adb command from Google's Android SDK? The way to get the log
is to connect your device to your computer via USB, and then to use this
command:

   adb logcat -v time -d >logfile

logcat is the adb command's function to copy out the log.
-v time means to include the timestamp on each line of the log.
-d means to dump the current log and then stop.
>logfile means to write the log to that file by redirecting standard output.

You can clear the log first via the command:

   adb logcat -c

Doing this before causing the problem is a good idea because, among other
things, it removes any possibly private data from the log. It also, of course,
keeps the captured log as small as possible.

--
Dave Mielke           | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014<tel:(613)%20726-0014> | Ottawa, Ontario   | http://Mielke.cc/bible/
EMail: Dave at Mielke.cc | Canada  K2A 1H7   | http://FamilyRadio.org/
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
--
Devin Prater
r.d.t.prater at gmail.com<mailto:r.d.t.prater at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mielke.cc/pipermail/brltty/attachments/20161214/e71263b9/attachment.html>