-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix, improve script for running waydroid in weston #44
base: master
Are you sure you want to change the base?
Conversation
Boruch-Baum
commented
Mar 20, 2023
- Running konsole as written doesn't work
- No need to sleep
- Added logic to show how to create a nicely proportioned waydroid window
1) Running konsole as written doesn't work 2) No need to sleep 3) Added logic to show how to create a nicely proportioned waydroid window
whats the point of the xdpyinfo stuff? when launching weston as the main compositor it should automatically chose the optimal resolution. also doesn't xdpyinfo need to be launched inside of a compositor? I don't see how this is useful for a waydroid only session. the sleep is used to make sure that weston has time to actually start up when launching a new session. exporting wayland session shouldn't be needed since waydroid will typically inherit it from inside the compositor. |
Hi. Thanks that someone has finally taken notice of the PR. I thought the project had gone stale or something.
I've been using this modification since I posted the code in March, over three months ago. |
all in all im not opposed, just a couple issues
|
I'm also using sddm (debian, version 0.19.0-5). My environment is debian
12 bookworm, kde (debian plasma-desktop version 4:5.27.5-2), weston
(debian version 10.0.1-1+b1). For me, this patch was also working before
the dist-upgrade to bookworm.
What should happen visually is that immediately there should appear a
weston compositor window in the 9:16 portrait dimensions with its
default background. Then it loads waydroid. For me, this has always been
an agonizingly slow process, even without the patch. It takes my system
about five to ten seconds to load waydroid. Waydroid immediately
displays by default for me an astronomy/nebula wallpaper and then loads the
icons of the installed apps that I've selected for my home screen.
Double-checked just now.
…On 2023-07-08 22:33, Mitchel Stewart wrote:
all in all im not opposed, just a couple issues
* This doesn't work for me when launching via SDDM, seems like it
needs more testing, what greeter did you use?
* the expectation for a lot of users is for it to be running using
the full screen, I'm not opposed to 16:9 form factor, but it should
be a separate entry, not a replacement, and should be made clear
the distinction between the two.
—
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
You are receiving this because you authored the thread. Message ID:
***@***.***>
References
1. #44 (comment)
2. https://github.com/notifications/unsubscribe-auth/AAOE3KEGZSUAK54DV75QI6LXPI7CZANCNFSM6AAAAAAWARHWEI
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
|
I agree about being user-friendly about the form factor.
IMO, waydroid should remember the sizing used last by the user. I mean
that if the user resizes a waydroid instance, that form factor should be
used on the next waydroid launch.
Additionally, there should be some kind of easily accessible relevant config
variable, and config file. As it stands, waydroid doesn't have any presence in
$HOME/.config ($XDG_CONFIG).
My memory is that it was because of my frustration with those issues that I put
the form factor snippet in the code in the first place -- ie. no config
option, and no resize memory.
…On 2023-07-08 22:33, Mitchel Stewart wrote:
all in all im not opposed, just a couple issues
* This doesn't work for me when launching via SDDM, seems like it
needs more testing, what greeter did you use?
* the expectation for a lot of users is for it to be running using
the full screen, I'm not opposed to 16:9 form factor, but it should
be a separate entry, not a replacement, and should be made clear
the distinction between the two.
—
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
You are receiving this because you authored the thread. Message ID:
***@***.***>
References
1. #44 (comment)
2. https://github.com/notifications/unsubscribe-auth/AAOE3KEGZSUAK54DV75QI6LXPI7CZANCNFSM6AAAAAAWARHWEI
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
|
wait, are you launching this from within kde as nested? these docs are for launching weston as the primary compositor and then running waydroid in that. I just verified and xdpyinfo does need to be launched inside of a compositor running from something like TTY wont work with this. |
I would suggest making this PR a separate doc entry for running as a nested window. |
From sddm, I'm running kde-plasma as a non-wayland session, and
launching weston/waydroid within that.
…On 2023-07-09 18:53, Mitchel Stewart wrote:
wait, are you launching this from within kde as nested? these docs are
for launching weston as the primary compositor and then running
waydroid in that. I just verified and xdpyinfo does need to be launched
inside of a compositor running from something like TTY wont work with
this.
—
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
You are receiving this because you authored the thread. Message ID:
***@***.***>
References
1. #44 (comment)
2. https://github.com/notifications/unsubscribe-auth/AAOE3KCU4H7VJXZWL67ZJVTXPNOCZANCNFSM6AAAAAAWARHWEI
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
|
yes, that is a nested session, this docs page is for using waydroid only as a single isolated session. however as electrikjesus it would be great to have a separate entry in the docs for nested sessions! |