Theo wrote:--
> Most Pi distributions are 32 bit, and Android builds are 64 bit
> - I'm not sure if 64-bit Android can run 32 bit binaries.

I thought my RPi-1 was 32bit? Not used now for lack of a display.

ARM Tablet: cat /proc/cpuinfo : shows ARMv7;
and the x86 Tablet was also 32bit. It had charging problems and failed.

 How do you open these damned things, when it fails ?

]> Where would I find such static-binaries ? Eg. a Forth interpreter,
]> some mouse-based program ...

> Compile them yourself, probably.
No! That's exactly the question. The static-binary: e3 editor was
marvelous in the X86 Tablet's TerminalEmulator.
There must be plenty 32Bit ARM static-binaries available.

Compiling opens a whole new can-o-worms.
That's one reason why I'm investigating Mulinux [1990s fd0:1.7byte]
which has most apps written in ash/busybox.

BTW Mulinux is mostly menu-based; and I copied & modified an ash-based
file-manager which I'd written long ago. It shows a numbered: `ls -tl`
 and the menu:--

R[move, V[iew, E[dit, cD[ir, U[cd ../, Q[uit, M[kdir, C[opy, F[ind  =
  So you don't need to eg. `ls -t|less ; nano `
  you just: 4 e
!! I've just realised for android: index by a-z is better ?
--------------
Previous posters here, have investigated KBox3 & 4, which the author is
discontinuing, because google/android makes it impossible to ajust to
their changes, with reasonable effort.
`chroot`-ing to a simulated  inside the TermlEmu,
seems just too problematic. So I've decided to accept the limitations of
ash -- which Android uses.
BTW. I'm writing/posting this from USBstik-based Tinycore & pasteing
lines to:
nc -vv -w 80 -n news.eternal-september.org 119 | tee -a TraceFile
 and I chose to accept Tinycore's default: non full X11.
It uses? pstree ==
init-+-Xfbdev
     |-aterm---sh---sh
     |-flwm
     ...
.. and Tinycore's default is also ash.
PS ? Is my  still wrong> ?

--- SoupGate-Win32 v1.05