speech-dispatcher and userspace chroot environment on Android

[Mgr. Janusz Chmiel]

I would like to inform every one of us about very positive findings related
to Speech-dispatcher and its compatibility with various speech engines. When
running it on userspace chrooted environment on Android devices.
Thanks to Pulseaudio for Termux, which provide robust and stable sound
server controllable by using Opensless protocol it is possible to perfectly
use speech-dispatcher with Espeak and Espeak-ng driver. Mbrola is also fully
compatible.
I will now test Speech-dispatcher with Festival. But I have one problem.
Festival must be run as A server. Is it possible to run it as A normal app
or is it really necessary to run it as A Linux service? Because systemd do
not function in chroot mode on ArchLinux at all.
I Am wondering, if would be possible to run Festival as A server but not
like a Linux service.

If it would be possible, It would be possible to work with Espeak, Mbrola
and even with Festival from Termux and Linux distribution executed thanks to
Proot Termux package.

Because it is even possible to use Evolution mail, Thunderbird, even
Seamonkey with ArchLinux AArch64, it brings a new possibilityes for all
visually impaired users. So  they can have benefit from using  little and
light veight Android devices. You can combine ANdroid with Linux. Because
Proot allow folder sharing, you can define shared folder to exchange data
between Linux distro and Android OS and even with The computer if you will
assign folder in The accessible file storage area for computers.

I have more than positive experience while using Speech-dispatcher and
Mbrola. No speech output quality issues, perfect stability, reliable char by
char browsing support not only on several editable fields. But really on all
situations even while browsing on Firefox or Seamonkey.

You are not being forced to use shared memory support native .so C library
for Linux distribution to use Speech-dispatcher And Espeak or Mbrola.
In fact shared memory support on Android have big senses only for some apps,
because complex shared memory allocations such as X11vnc is not compatible
with Androidshmem.so.
So if somebody is being afraid about security, no problem. Shared memory is
not necessary even for Mate desktop, because Mate developers have coded
their environment even for situations, where shared memory will not be used
at all.
Because security is big problem today thanks to powerful hackers all around
The world, I will be intensively debate with some professionals about
encrypting installed Linux distro on Android. It will be necessary to
develop compromise solution related to performance, internal chip
overburning problems. Because some Android devices have allready enabled
their internal data encryption so encrypting some data is even impossible.
But because Termux is Android app, Android build in security mechanishms are
not affected. Every one can encrypt his device, protect it by using password
or A fingerprint. So I think, that there is really not dangerous issue which
would prevent users to use Arch Linux on Android.
This dream is only possible thanks to Orca and Speech-dispatcher.
Because none of those apps enforces shared memory. Fortunately not only for
Me.