The only one solution will be to use some free app on Google Play for
fetching logcat messages while running. Because Android logs are
changing very fast. Second solution is to use Android platform tools,
connect Device to USB cable on A computer. I will try to fetch The
logcat messages. I
[quoted lines by Mgr. Janusz Chmiel on 2018/04/07 at 09:05 +0200]
>Here is procedure to reproduce The USB Braille device issue on Brltty
Do you know how to capture a log that covers the time of the failure?
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke
Dear Mr Mielke,
I wish you good Saturday morning.
Here is procedure to reproduce The USB Braille device issue on Brltty
for Android.
Use Brltty and when system do not send data to Braille device,
disconnect it.
Try to use Talkback as normally for several minutes. You should get
warning
[quoted lines by Mgr. Janusz Chmiel on 2018/04/06 at 21:15 +0200]
>How complex would be for you to implement some hod keys combination,
>which would enable Brltty for Android users suspend The service.
It's easy to disable the service, but, without it running anymore, it's not
possible to get
Dear MR Mielke and others,
I have big plea addressed to you, even I know, that it is not easy issue.
How complex would be for you to implement some hod keys combination,
which would enable Brltty for Android users suspend The service.
Talkback allow suspend itself by pressing two volume
I Am very sorry that I Am intruding you and mailing list with this topic
for so long time.
But really. Brltty program do not react on specific build in on Braille
display keys presses. But NVDA can detect pressed keys. I have also
terminated NVDA. May be, that The reason of my issue is caused
[quoted lines by Mgr. Janusz Chmiel on 2018/04/06 at 18:50 +0200]
>Please, are you sure, that compiled Brltty 5.6 includes algorithm for
>detecting keys for controlling Brltty from Braille display?
>I Am afraid, that it only work for Linux release of Brltty.
Yes, I'm very sure. The code is the
Dear MR Mielke,
Please, are you sure, that compiled Brltty 5.6 includes algorithm for
detecting keys for controlling Brltty from Braille display?
I Am afraid, that it only work for Linux release of Brltty.
___
This message was sent via the BRLTTY
[quoted lines by Mgr. Janusz Chmiel on 2018/04/06 at 14:47 +0200]
>Please, which key combination do I have to press?
For a Voyager, it's Thumb2+Dots1234. You can find all of the Voyager's key
bindings documented online as follows:
Go to: brltty.com
Click on: Documentation
Click on:
Please, which key combination do I have to press?
I can not find it inside included documentation.
I have pressed many various Braille device button, but nothink.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail
Oh, thank you very much. I did know that Brltty can be used for its
configuration. So I will terminate NVDA and I will check it out. Thank
you very much.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to:
[quoted lines by Mgr. Janusz Chmiel on 2018/04/06 at 09:57 +0200]
>Please do you think, that it is possible to set DOT pressure on
>Tieman Braille Voyager while using non original .sys driver from
>Tieman?
this should already be supported. Look in the Presentation submenu of the
preferences
Please do you think, that it is possible to set DOT pressure on Tieman
Braille Voyager while using non original .sys driver from Tieman? So by
using Libusb? Do you think, that it could be incorporated new
configuration Brltty item, which can specify DOT pressure and that this
function would
I have very probably solved my issue. I plugged Tieman Braille Voyager
to USB 2.0 port. Problem was really caused by The fact, that I have used
UsB 3.0 port. So I can use positive aspects of yours latest Brltty for
Windows.
And CPU is even less working, USB 3.0 is really not ideal connection
[quoted lines by Brian Tew on 2018/04/05 at 18:46 -0500]
>I sure did not realize a bad make file could trash the system. I will avoid
>installing as root if possible.
When you're logged in as root, any command will be allowed to blindly go ahead
and do its thing. We all wish that everone who
I sure did not realize a bad make file could trash the system. I will avoid
installing as root if possible.
I didn't even realize uninstalling 5.3.1 would remove the brltty.service file,
sheesh.
Perhaps you begin to discern the level of my ignorance.
I will eventually go back and do things the
Dear professionals,
Let Me express you my deepest possible appreciation to this Brltty for
Windows release. I would like to congratulate MR Tibault and others, who
have released this amazing application. Yours deepest possible
appreciation should be expressed thanks to very professional memory
Remember that locate only changes once per day, so it may be obsolete
by the time you were looking. Maybe be better to do a find instead.
On Thu, 05 Apr 2018 08:50:59 -0400,
Adrian van Bloois wrote:
>
> On Thu, Apr 05, 2018 at 05:16:26AM -0500, Brian Tew wrote:
> > Or
> >
> > Could root just
[quoted lines by Brian Tew on 2018/04/05 at 05:12 -0500]
>I made the changes in /etc/default/brltty that John mentioned.
There was no need as brltty (albeit, the installed one) was running.
>I apt-got purged 5.3.1
Well, I tried to advise to not do that.
>and recompiled 5.6 as root.
It's a
On Thu, Apr 05, 2018 at 05:16:26AM -0500, Brian Tew wrote:
> Or
>
> Could root just mv brltty to /sbin ?
Yes it could, but you will be stuck when you make the next upgrade.
>
> ___
> This message was sent via the BRLTTY mailing list.
> To post a
On Thu, Apr 05, 2018 at 05:12:26AM -0500, Brian Tew wrote:
> Ok I think there is just one more hurdle.
> I made the changes in /etc/default/brltty that John mentioned.
> I apt-got purged 5.3.1 and recompiled 5.6 as root.
> All went well, but when root tried to edit
You need a file in /etc/default called brltty and you should have
RUNBRLTTY=YES in that file -- you may already have it. Then you can
change the /bin/brltty in that same line to your version. This is
something Debian specific. The file in /lib is the correct one for Debian.
On Tue, 03 Apr 2018
[quoted lines by Brian Tew on 2018/04/03 at 12:10 -0500]
>/usr/lib/systemd/system does not exist. /usr/lib/systemd does exist, but
>theres no system directory in it.
That's okay. Each distribution does things its own way. Since I can't look
directly at yours, the best I can do is make
On Mon, Apr 02, 2018 at 03:51:09PM -0500, Brian Tew wrote:
> WellI don't know what to try next.
> 5.3.1 works fine, so I'm not in trouble, but 5.6 would be nice.
> I was thinking of the following:
> rm all brltty directories recursively, apt-get purge 5.31 and recompil.
> What do yall think?
> I
[quoted lines by Brian Tew on 2018/03/31 at 14:48 -0500]
>attached are /usr/local/brltty-5.6/config.log and the entire compile ane
>-ldebug.
There were no attachments.
>I can't believe anybody can go through all this.
It's a matter of knowing where might be interesting places to look.
--
I
[quoted lines by Brian Tew on 2018/03/31 at 11:19 -0500]
>trying to send the config.h and config.mk files.
>they are attached if that works.
Got them. Thanks. I don't see anything obviously wrong in them (so far,
anyway). Perhaps config.log and the -ldebug output might shed some light on the
[quoted lines by Brian Tew on 2018/03/31 at 09:03 -0500]
>the -ldebug option spews out over three thousand lines, lol.
It'd be better to also use the -L (uppercase) option to specify a file for
brltty to write its log to. Then (which would be helful) you could post that
log file for us to look
Hi. I am coming late to this thread, but I know that the prefix is
wrong. If you leave this out then brltty will install
in/usr/local/... which is what I think you may want. If the prefix is
wrong, everything else after that will not work correctly. So, clean
the directory
[quoted lines by Didier Spaier on 2018/03/25 at 23:36 +0200]
>This should means that you are building on a system without systemd installed,
>I think.
Yes, or it could also be that systemd is being used but that the systemd
developer package isn't installed.
>As brltty works without it,
rltty.com>
To: Informal discussion between users and developers of BRLTTY.
<brltty@brltty.com>
Subject: Re: [BRLTTY] 5.6 is now released.
[quoted lines by 高生旺 on 2018/02/13 at 13:09 +0800]
My build commands:
./autogen
./configure --with-init-path=/sbin/init
make
Is this immed
[quoted lines by 高生旺 on 2018/02/13 at 13:09 +0800]
>My build commands:
>./autogen
>./configure --with-init-path=/sbin/init
>make
Is this immediately after a git clone into a fresh directory?
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke | 2213
scussion between users and developers of BRLTTY.
<brltty@brltty.com>
To: Informal discussion between users and developers of BRLTTY.
<brltty@brltty.com>
Subject: Re: [BRLTTY] 5.6 is now released.
[quoted lines by 高生旺 on 2018/02/13 at 11:47 +0800]
Your configure script looks fi
[quoted lines by 高生旺 on 2018/02/13 at 11:47 +0800]
Your configure script looks fine. Perhaps, just to be sure, update to the
latest code and try again. Please let me know exactly which commands you
execute to do the build. Also, after the configure, let me know if the
LOUIS_LIBS line in
[quoted lines by Samuel Thibault on 2018/02/12 at 21:54 +0100]
>> Could you please try changing that AC_PATH_PROG (line 353 of configure.ac)
>> to
>> AC_PATH_TOOL (same syntax) as perhaps a simpler way of resolving the problem?
>
>That seems to be working fine indeed.
Thanks. Done.
--
I
Hello,
Dave Mielke, on dim. 11 févr. 2018 14:59:02 -0500, wrote:
> Could you please try changing that AC_PATH_PROG (line 353 of configure.ac) to
> AC_PATH_TOOL (same syntax) as perhaps a simpler way of resolving the problem?
That seems to be working fine indeed.
Samuel
[quoted lines by 高生旺 on 2018/02/12 at 12:20 +0800]
>Atached. Thanks!
The problem is, that for some reason I'm not understanding, your config.mk
contains:
LOUIS_INCLUDES =
LOUIS_LIBS = ""
Your log shows that liblouis isn't installed, so both these make macros should
be empty. The way
[quoted lines by 高生旺 on 2018/02/12 at 10:44 +0800]
>Log file attached. Thank you!
Please also post your config.mk and config.log files.
--
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:
rs of BRLTTY.
<brltty@brltty.com>
Subject: Re: [BRLTTY] 5.6 is now released.
[quoted lines by ??? on 2018/02/12 at 10:00 +0800]
While building the last code, I got the error:
gcc: error: : No such file or directory
What's wrong and how to check and fix it?
It means that a sour
[quoted lines by 高生旺 on 2018/02/12 at 10:00 +0800]
>While building the last code, I got the error:
>
>gcc: error: : No such file or directory
>
>What's wrong and how to check and fix it?
It means that a source file is missing. That, of course, shouldn't happen.
Please post the full make log so
While building the last code, I got the error:
gcc: error: : No such file or directory
What's wrong and how to check and fix it?
Please someone help me. Thank you!
Coscell
___
This message was sent via the BRLTTY mailing list.
To post a message, send
[quoted lines by Samuel Thibault on 2018/02/11 at 17:53 +0100]
>While working on the Debian package, I got the following warning which
>got recently added to Debian:
>
>autotools-pkg-config-macro-not-cross-compilation-safe
>
> The package appears to use AC_PATH_PROG to discover the location of
>
Hello,
Dave Mielke, on lun. 05 févr. 2018 12:02:34 -0500, wrote:
> Release 5.6 of brltty is now available.
While working on the Debian package, I got the following warning which
got recently added to Debian:
autotools-pkg-config-macro-not-cross-compilation-safe
The package appears to use
42 matches
Mail list logo
