I Am running several Linux distributions on my Android devices. I would like to ask somebody of us, if Dbus-broker does support Android kernel system calls? So Dbus-broker can be used even in userspace mode when Android and not real Linux kernel is being used.

Why I want to use dbus-broker on my Android devices?

Because The Dbus-broker speed up interprocess communication. Especially when reading long list of E-mail messages while working with many thousants of E-mail messages while using Seamonkey E-mail client.

Please could someone of us try to invent The commands, which could be executed to allow Dbus-broker work on Android kernel?

I Am using Termux and Proot special C binary, which uses Btrace to change and retranslate system calls and folders name to allow to run Linux on Android.

Sure. There are plenty of limitations, which are being caused by The difference between real Linux kernel and Android kernel.

It is not possible to use Qemu on cheap Android phones. Only expensive Pixel phones support Kqemu hardware virtualisation directly on their CPU level. But those expensive models of Android devices are out of my scope.

Running Qemu and real Linux kernel does have sense only for developers, who want to run less intensive tasks. I can not boot Opensuse and run Mate and Orca while using Qemu in user mode.

Rooting phones is not easy and it can corrupt phones firmware.

Proot is The best available alternative.

So if someone of us could describe how to start dbus-broker on Android, I will be very positively impressed.

I have been able to use Orca, Mate desktop and Tuner Internet radio while using The latest available Opensuse packages for AArch64 architecture.

Unfortunately, using Seamonkey is very very slow. So I Am hoping, that Dbus-broker will speed it up.

Normal Dbus work normally.