Question regarding shared memory Android 11 in debian proot #24
Comments
|
Forgot to say thank you for your app! |
|
It looks like you messed up with run environment of /system/bin/sh \
"$DATA_DIR/proots/linuxcontainers-debian-buster/run" \
0:0 ./wlstart-X | \
/system/bin/sh \
"$DATA_DIR/proots/linuxcontainers-debian-buster/run" \
'' ./wlstart-WMIt must be run in the Android own shell and start all the other scripts by itself (in order to sync the security tokens). Please, see updated (green-green-avk/AnotherTerm-docs@a64c2c5) |
|
Please, also take into account this workaround: #25 (comment). |
|
And this workaround: Neo-Oli/termux-ubuntu#35 (comment). |
|
Thanks for the update! I have created a new terminal with the execute command thanks to your shortcut. I'm still not sure where to put the shared memory api commands below:
I tried executing the statements in a debian terminal session but I have no clue if that is correct or has the intended effect. I get the following error when I subsequently run a second separate graphical debian session (with the execute setting):
Thanks for your time! |
It is already in the start-up scripts: https://green-green-avk.github.io/AnotherTerm-docs/graphical-sessions.html#script-startwm
|
|
Hi, that error happens but the script does not appear to exit, it just hangs. No graphical session is started. Thanks |
|
Hi, the script in that case just halted and showed that result. No graphical session started. and it freezes there. |
|
So, when you are going back to the sessions list, you see no graphical session in it??? The log looks like it is perfectly connected to the Wayland backend... |
|
I'm sorry I didn't realize the session would appear separately, and I was able to go into the graphical session successfully! Below is the session log: I was not able to execute anything, maybe I need to install more of the xfce environment via tasksel so it can find everything. I also was not able to type into any dialog boxes, but that might be a result of the missing programs? I think the log indicates pm-is-supported is missing, I can look that up. I'm using Samsung Dex, and the window works perfectly on the attached screen. Resizes quickly and correctly on my limited testing. So the only issues I see at this point are missing programs and can't type. |
|
Ok, running apt install task-xfce-desktop did the trick to populate the programs. There is now a quirk, there are two mouse cursors showing, which is more annoying than a problem. Also there is still a keyboard issue. Backspace and cursor keys don't work on my keyboard but they do work on the built in anotherterm onscreen keyboard. So that makes desktop use problematic. But thanks because I definitely appreciate the potential! |
|
Uh huh... Vendor's own external keyboard mapping Please, also take into account this one: #26 |
|
And this one: #27 |
|
Tried another keyboard, a nexdock 360 connected via usb, but the backspace key did not work. I will try more if I get a chance. I also tried to see if remapping keys might help, but could not figure that out. CTRL-H does work for backspace, and ctrl-B,F for cursor. So hardware keyboards can work with workarounds. |
|
Addendum to above,,,,,, I was able to start tigervnc scraping server on the buster session, and connect to that vnc session after starting the graphical wayland session. I connected using the client avnc. I was able to use the backspace and arrow keys in the vnc session which mirrored the wayland session. Wayland still didn't work. Thanks! |
|
Did backspace and cursors not work in any screen keyboard mode (Off, Built-in, IME)? |
|
I can't get them to work when the anotherterm built in soft keyboard is active or when it is toggled off. I am not sure how to have the system soft keyboard pop up when the hardware keyboard is attached so I don't know for sure, I have to look further.
Dimitri Vlahakis
e. ***@***.***
c. ***
On November 11, 2021 at 4:27 PM, green-green-avk ***@***.***) wrote:
Did backspace and cursors not work in any screen keyboard mode (Off, Built-in, IME)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub ( #24 (comment) ), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AOYL7UUZYPR4SUVWOHPXQALULQYNJANCNFSM5HTXAM5Q ).
|
|
Sorry, I forgot that IME cannot be shown when an external keyboard is attached. |
|
I had also run xev from a terminal because I was trying to see if the keys were registering under the graphical Wayland session. The backspace and cursor keys did not register anything at all for xev. So remapping was not an option I guess.
Dimitri Vlahakis
e. ***@***.***
c. ***
On November 11, 2021 at 6:12 PM, green-green-avk ***@***.***) wrote:
Sorry, I forgot that IME cannot be shown when the hardware keyboard is attached.
Funny: I blocked this combination as a workaround for non-working hardware keyboard Backspace in older Androids...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub ( #24 (comment) ), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AOYL7UVDBIOH4OX6M2FP5GLULREUFANCNFSM5HTXAM5Q ).
|
|
By the way, do the external keyboard backspace and cursor keys work in the ANSI terminal sessions? |
|
Yes, they work normally in the default anotherterm terminal sessions.
Dimitri Vlahakis
e. ***@***.***
c. ***
On November 12, 2021 at 1:33 PM, green-green-avk ***@***.***) wrote:
By the way, do the backspace and cursor keys work in the ANSI terminal sessions?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub ( #24 (comment) ), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AOYL7UQP7PD3MVPWU7XT4T3ULVMZDANCNFSM5HTXAM5Q ).
|
|
Oops... I see it too. Thank you, for providing me with some inspiration to finish the work. One more question: do you prefer to see several keyboards as either separate devices (in terms of Wayland protocol) or one aggregate device? |
|
Thanks for the app! I appreciate the effort and the result.
I'm not sure I understand, do you mean separate keyboards in the Wayland proot environment? I often switch from hardware to soft keyboards, because I move around for work, so I appreciate being able to easily pick the one that works best at the moment. I hope that answers your question.
Dimitri Vlahakis
e. ***@***.***
c. +***
On November 12, 2021 at 3:44 PM, green-green-avk ***@***.***) wrote:
Oops... I see it too.
Thank you, for providing me with some inspiration to finish the work.
One more question: do you prefer to see several keyboards as either separate devices (in terms of Wayland protocol) or one aggregate device?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub ( #24 (comment) ), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AOYL7URUAW2HSGOXMTQ3HZ3ULV4BZANCNFSM5HTXAM5Q ).
|
|
Ok. I'll try to do it in the best possible way. |
|
Hello. I just installed the graphical window in my debian bullseye session, and it is working very well. I was able to run two graphical sessions, which is a great bonus! I can confirm the backspace and cursors do not work in bullseye also though. Also as an aside in case there were edit notifications I removed my phone number which I noticed in prior comments I made, sorry. Thanks again! |
|
MkIV-dev16
Let's try it. |
|
Hello. I tried to execute the debian buster and bullseye wm sessions I used before to test the keyboard, but I get the following error log where it used to work (My samsung has updated to Android 12 in case that might have an effect). Any suggestions as to what I am doing wrong? `/usr/bin/startxfce4: X server already running on display :0 (xfce4-session:11687): xfce4-session-WARNING **: 06:45:14.385: gpg-agent returned no PID in the variables (xfce4-session:11687): xfce4-session-WARNING **: 06:45:14.388: xfsm_manager_load_session: Something wrong with /home/my_acct/.cache/sessions/xfce4-session-localh (xfsettingsd:11718): libupower-glib-WARNING **: 06:45:14.812: Couldn't connect to proxy: Could not connect: No such file or directory (xfsettingsd:11718): libupower-glib-CRITICAL **: 06:45:14.812: up_client_get_lid_is_closed: assertion 'UP_IS_CLIENT (client)' failed (xfsettingsd:11718): GLib-GObject-WARNING **: 06:45:14.815: invalid (NULL) pointer instance (xfsettingsd:11718): GLib-GObject-CRITICAL **: 06:45:14.821: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (polkit-gnome-authentication-agent-1:11743): polkit-gnome-1-WARNING **: 06:45:14.942: Error getting authority: Error initializing authority: Could not connect: N ** (light-locker:11716): ERROR **: 06:45:14.955: session_id is not set, is /proc mounted with hidepid>0? import dbus.glib (nm-applet:11748): nm-applet-WARNING **: 06:45:15.134: Error connecting to system D-Bus: Could not connect: No such file or directory (nm-applet:11748): nm-applet-WARNING **: 06:45:15.136: Could not connect: No such file or directory (xfsettingsd:11718): xfsettingsd-WARNING **: 06:45:15.318: Failed to get the _NET_NUMBER_OF_DESKTOPS property. (xfdesktop:11711): GVFS-RemoteVolumeMonitor-WARNING **: 06:45:15.715: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported (xfwm4:11703): xfwm4-WARNING **: 06:45:15.823: Error opening /dev/dri/card0: Permission denied (xfce4-session:11687): xfce4-session-WARNING **: 06:45:15.980: failed to run script: Failed to execute child process “/usr/bin/pm-is-supported” (No such file or (xfce4-session:11687): xfce4-session-WARNING **: 06:45:15.985: failed to run script: Failed to execute child process “/usr/bin/pm-is-supported” (No such file or (nm-applet:11748): libnm-CRITICAL **: 06:45:16.070: ((libnm/nm-client.c:271)): assertion '' failed (nm-applet:11748): libnm-CRITICAL **: 06:45:16.071: ((libnm/nm-client.c:232)): assertion '' failed (nm-applet:11748): libnm-CRITICAL **: 06:45:16.428: ((libnm/nm-client.c:989)): assertion '' failed |
|
Hello. I'm getting the following error when running the graphical session (debian bullseye). Νοt sure I followed the instructions correctly for libwrapdroid or if something needs to be done, but regardless this is the output i get upon starting the session. Thanks! Traceback (most recent call last) |
|
Hmm... |
|
Hi! It is android 12. One ui 4.1 on a galaxy note 20. Thanks! |
|
Did Wayland stop working after a system update? |
|
And try to run |
|
Wayland stopped working after the update to oneui 4 on my system, which was I guess the switch to android 12. To be fair I had not run it for a little while, but I have not made any other major changes. I tried reinstalling the proot and wm, but that did not solve the problem. I just ran termsh and it does display a long help message after the following error: WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" Thanks! |
|
Hmm... Your Android 12 even does not have a |
|
The graphical window is working for me now. I am using a debian buster container, and typing this in firefox. I'm using Samsung Dex and , and the window is sizing nicely and is stable. The keyboard on my nexdock is working perfectly also. |
|
Which flavor do you use? I recommend oldgood as it targets Android 9 and thus declares older and less strict compatibility rules. |
|
I am using the redist flavor on my samsung note 20 ultra. Should I install the oldgood flavor over it? |
|
Each flavor has its own app id. |
|
Got it. Thanks! |
Hi. I'm trying to install wayland support on a debian bullseye proot. I have the mkiv beta latest release.
I have installed the scripts according to the instructions I believe. First libwrapdroid and then I run the commands:
Then I run the execute commands listed:
and I get the following output
CANNOT LINK EXECUTABLE "CANNOT LINK EXECUTABLE "/system/bin/sh/system/bin/sh": ": library "libpthread.so.0" not found: needed by /opt/shm/lib/libwrapdroid-shm-sysv.so in namespace (default)library "libpthread.so.0" not found: needed by /opt/shm/lib/libwrapdroid-shm-sysv.so in namespace (default)I also did an ls to see if libpthread exists, and I get the below, which is also unclear to me because it says it is not there but it is. Actually, that is another issue for the proot, but I'm not sure it is related. I get this error for all the files in /lib. This doesn't happen for ubuntu focal proot:
ls: cannot access '/lib/aarch64-linux-gnu/libpthread.so': No such file or directoryThe text was updated successfully, but these errors were encountered: