Conversation
01b282d to
03c97b6
Compare
|
Very good thank you I will add them and maybe I'll try to add more |
03c97b6 to
50254b1
Compare
50254b1 to
223dbf4
Compare
|
@robertkirkman can you check if just running |
|
@robertkirkman can you try this patch then launch with just |
|
But it can't launch app |
Yes with just |
What does the patch do? I tried it, and for me it is still necessary to run |
If you have adreno make sure to use |
i was just trying to run them without system bus 😅 |
|
wait let me share a screen record of my device |
|
for some reason it decide to work when i was recording :- https://drive.google.com/file/d/1_qvUG7OH6-F_-2eLFKGSAucKbHPSjA91/view?usp=sharing but in most of the case this is what was happening:- https://drive.google.com/file/d/19sPJdPRZh0aNUZHWNWEqMbS6u_pQUJPQ/view?usp=sharing |
|
I tried to work on version 49, but as we know, version 49 has a strong dependency on a dependency-based init system, with a default at Systemd and the option to implement additional backends, and currently the only additional backend widely known to have been implemented at this time is this one for OpenRC: https://github.com/swagtoy/gnome-session-openrc If someone else implements another backend in the future that can restore self-launching of GNOME, then I could progress more by copying that. (I assume the distro with the most maintainers likely to do that is FreeBSD) I tried to figure out if there is a way to manually write out the commands which the init system needs to execute in order one by one for GNOME 49 to complete its launch sequence, but I haven't been able to yet unfortunately. I think it might involve a combination of Something I might be able to try is wrapping those executables with scripts that log their activities with timestamps on a Systemd or OpenRC distro, then launch GNOME there, then check the log timestamps to construct a sequence of commands necessary to launch GNOME 49. |
|
Alpine Linux has moved forward with the rest of GNOME 49 except for https://gitlab.alpinelinux.org/alpine/aports/-/commit/349a5ed70ff9d89e5c6af01f31078cc9b59bb8e3 I could probably do that now, but if many other distros also do that, then I expect a community-maintained fork or patchset of |
diff --git a/gnome-session/main.c b/gnome-session/main.c
index 5f98149..64a1aab 100644
--- a/gnome-session/main.c
+++ b/gnome-session/main.c
@@ -518,6 +518,11 @@ main (int argc, char **argv)
gsm_util_init_error (TRUE, "%s", error->message);
}
+ /* Termux Hack: Start dbus-daemon --system first before anything */
+ g_message ("Termux Hack: starting system dbus-daemon...");
+ remove ("@TERMUX_PREFIX@/var/run/dbus/pid");
+ system ("dbus-daemon --system --fork");
+
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.@robertkirkman can we not do something like this so we don't have to do that extra |
|
Yes it's a good idea I might add that, though, the hard part is that I would want to actually make sure that |
|
ok i will try to do that |
|
we can get the pid like this $ cat "/data/data/com.termux/files/usr/var/run/dbus/pid"
$ 9208 |
diff --git a/gnome-session/main.c b/gnome-session/main.c
index 5f98149..28d8975 100644
--- a/gnome-session/main.c
+++ b/gnome-session/main.c
@@ -518,6 +518,23 @@ main (int argc, char **argv)
gsm_util_init_error (TRUE, "%s", error->message);
}
+ /* Termux Hack: Start dbus-daemon --system first before anything */
+ {
+ const char *pid_file = "@TERMUX_PREFIX@/var/run/dbus/pid";
+ FILE *f = fopen (pid_file, "r");
+ if (f) {
+ int pid = 0;
+ if (fscanf (f, "%d", &pid) == 1 && pid > 0) {
+ g_message ("Termux Hack: Killing stale system dbus-daemon (pid %d)", pid);
+ kill (pid, SIGTERM);
+ }
+ fclose (f);
+ }
+ remove (pid_file);
+ g_message ("Termux Hack: starting system dbus-daemon...");
+ system ("dbus-daemon --system --fork");
+ }
+
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.what about this ? |
ad3e7cb to
aaf2dec
Compare
|
Yes that's good thank you I tested that and it's working |
|
Just asking but can you guys later make a tutorial on this installation and perhaps setup requirements because this looks really amazing to me. I want to try running this on my phone |
|
@23xvx hi, I made this video of how to download PR artifacts, you would download this just like in this video except just make sure you are logged into GitHub so you can see the download URL, and click on this PR instead of the one in the video, everything else is the same, then after you install it just use this command: LIBGL_ALWAYS_SOFTWARE=1 termux-x11 -xstartup gnome-sessionartifacts.webmit will open |
|
|
Another quick question but is it normal for the desktop to be laggy/glitchy because sometimes it takes time to respond when opening an app or just switching to another window |
Yes it's because it has software rendering and GNOME is probably not really going to work on android with hardware accelerated GPU connection. so the CPU performance is fine but the GPU performance is not going to be good. |
|
if you have both turnip ( |
I see |
e398615 to
fee5ca5
Compare
- Alternative build of termux#24585 - Fixes termux#10173 - How to use this build: ```bash export LIBGL_ALWAYS_SOFTWARE=1 termux-x11 -xstartup gnome-session ``` Co-authored-by: Chongyun Lee <licy183@termux.dev> Co-authored-by: Md Arif <111168803+sabamdarif@users.noreply.github.com>
fee5ca5 to
6313cb9
Compare




Alternative build of [WIP] GNOME Shell #24585
Fixes Package request: Gnome shell #10173
How to use this build: