Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Boruch-Baum
Copy link

  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

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
@Quackdoc
Copy link
Contributor

Quackdoc commented Jul 8, 2023

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.

@Boruch-Baum
Copy link
Author

Hi. Thanks that someone has finally taken notice of the PR. I thought the project had gone stale or something.

  1. About xdpyinfo:
    1a) As I wrote in the commit's comment, it's "logic to show how to create a nicely proportioned waydroid window"
    1b) The prior code does NOT "choose the optimal value", it seizes all of its parent's windows size, which for many people running a desktop will be undesirable. In my case, my desktop has a modern 'wide' (landscape) screen, but my expectation for android emulation is for the presentation to be similar to that of my phone, in 'thin' (portrait) layout. The code snippet fetches the parent window's dimensions, and applies the golden ratio to it's height to produce a width value.
    1c) It does, and it is.
    1d) Back to '1a', above.

  2. About the 'sleep'. With my code, the sleep is unnecessary. Three seconds is also a really long time.

  3. About "exporting wayland session". The ID of the session most definitely did need to be set, and then be exported. That was part of the trial-and-error experience behind getting the snippet to work.

I've been using this modification since I posted the code in March, over three months ago.

@Quackdoc
Copy link
Contributor

Quackdoc commented Jul 9, 2023

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.

@Boruch-Baum
Copy link
Author

Boruch-Baum commented Jul 9, 2023 via email

@Boruch-Baum
Copy link
Author

Boruch-Baum commented Jul 9, 2023 via email

@Quackdoc
Copy link
Contributor

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.

@electrikjesus
Copy link
Member

I would suggest making this PR a separate doc entry for running as a nested window.

@Boruch-Baum
Copy link
Author

Boruch-Baum commented Jul 10, 2023 via email

@Quackdoc
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants