[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

shared memory and chroot containers on Android devices



Dear elite developers,

           I have found out very sad fact. More and more apps are using shared memory more and more intensively. This fact is very probably good for all users, who are running their apps with full Linux Debian kernel. But if user want to run such app on chroot container executed by using Proot and Termux, it is challenging.

Not so much for sighted majority. But if user uses Orca screen reader which uses inter proces communication very intensive, such apps can get rather unusable.

The good example is Firefox-eser and Chromium.

Chromium even crash without full shared memory support.

The question is, what we can do?

One elite C language developer MR ZhymabekRoman has done his best to implement shared memory support to Proot Binary directly.

 

But unfortunately, it is still not enough.

Does somebody of us think, that it would be even possible to add all shared memory functions like are in full Linux kernel by implement them on userspace app?

Or it is 100 % impossible?

 

Chromium need shared memory, and unfortunately,FIrefox too.

Latest Seamonkey stable do not work, it is very probably not thanks to shared memory. But it is also sad fact.

 

I do not know, why Samsung company could develope some technique, that full Linux kernel could be used on some Android models with no need to even reboot device and without Qemu?

 

Is it possible to execute other kernel with no need to use Qemu if Android kernel run also in memory?

 

Rooting devices is really not very easy task for totally blind users.


Reply to: