ARM static-binaries for Android?

RPi users seem suitably experienced/qualified to help overcome the problems of using ARM-based-android. Eg. for Tablets, which Google doesn't want us to use independently of their financial model.

Have you seen the output [via a terminal emulator] of: pstree -p For: pstree -p | wc -l I get 652 ! twitter seems to run over 40 , although I've never used it.

A previous X86 Android-Tablet [which konked, because of the absurd microUSB charging port being worn out by need to recharge the greedy PID crowd] ran e3: the good x86 static/no-dependencies 13Kb editor.

Can RPi static-binaries also be expected to run in ARM-tablet TermEmu? Where would I find such static-binaries ? Eg. a Forth interpreter, some mouse-based program ...

== TIA.

PS. Are any RPi users 'looking into' Inferno ? From `pstree -p`: my attemped install, shows 10 PIDs descendant from: uova.inferno_os but nothing shows on the screen when it's launched.

Reply to
nc4NNTP
Loading thread data ...

Using the -p option shows all copies of forked processes (threads?) while not using it shows each type of process once.

The short answer to your question is "probably not", because:

- Android uses its own build of the Linux kernel, which may differ radically from the versions we use on Raspis and normal PCs

- the Android package manager is almost certainly different from anything used by other distros such as Debian or Fedora

- IIRC all its graphic superstructure (desktop and its applications) are written in Java and bear little or no relation to the desktop equivalents used on phones and tablets.

If you want to run Forth and other development tools for non-Andriod distros, get a RaspberryPi. You may still be able to use a tablet as a terminal provided that you can find an SSH package that runs on it, though the lack of keyboard and mouse feels like a handicap to me.

--
Martin    | martin at 
Gregorie  | gregorie dot org
Reply to
Martin Gregorie

To go completely Google-free take a look at LineageOS

formatting link

--
Dave
Reply to
Dave

$ pstree -p | wc -l

35
--
To ban Christmas, simply give turkeys the vote.
Reply to
The Natural Philosopher

Assuming the same architecture (aarch64 etc), in principle yes. The Linux kernel interface is mostly unchanged, and a terminal app will run a shell. Anything you choose to interact with (eg GUI) is your own problem - you'd have to run your own X server or whatever and access it over the network, since the tablet isn't running X. You'd need to use Android APIs to use the native UI.

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.

Compile them yourself, probably.

Theo

Reply to
Theo

Theo wrote:--

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 ...

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> ?

Reply to
qhsgrant

On Wed, 27 Feb 2019 10:47:51 -0000 (UTC), snipped-for-privacy@outlook.com declaimed the following:

The R-Pi 3 series are quad-core 64-bit processors. However, the standard OS install (via NOOBS, and likely also the stand-alone Raspbian, et al) are 32-bit to support all R-Pi models with a single installer.

AS for the later queries about "static binaries" -- I would expect them to be very rare, as they have to be built with all needed library functions included, and that starts to add up fast on a limited memory system, in contrast to run-time shared object libraries.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/
Reply to
Dennis Lee Bieber

Long time since this troll has been posting on here.

Reply to
mm0fmf

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.