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

After activating multi-window mode, no app starts anymore if color inverse setting is enabled. #131

Closed
PhilDevProg opened this issue Oct 3, 2021 · 14 comments

Comments

@PhilDevProg
Copy link

PhilDevProg commented Oct 3, 2021

After I enabled multi-window mode with waydroid prop set persist.waydroid.multi_windows true and restarted the container no app starts anymore.
I'm on ZorinOS 16(Ubuntu 20.04) with GNOME 3.38.4 and color inversion.

IssueVideo.mov
@karuboniru
Copy link

In case you need logs
waydroid_log.txt
dmesg.txt
logcat.txt

For more information, I am on Fedora 35 with self packaged waydroid package

The problem exists on both SELinux on Enforcing/Permissive mode. waydroid-session seems to be working with [23:28:14] Android with user 0 is ready output. waydroid app launch com.android.calculator2 triggers some logs in logcat. Seems to be some display problem?

@ahmed2m
Copy link

ahmed2m commented Oct 25, 2021

I observed this behavior when the multiwindow AND the color inverse setting (in the setting app) are both enabled

@electrikjesus
Copy link
Member

Disable The invert color setting from within Android using full screen UI and you should be able to use multi-wind mode properly

@PhilDevProg
Copy link
Author

Yes, it works now.

@PhilDevProg PhilDevProg changed the title After activating multi-window mode, no app starts anymore After activating multi-window mode, no app starts anymore if color inverse setting is enabled. Oct 25, 2021
@Genxster1998
Copy link

@PhilDevProg + instead use patched mutter and waydroid prop for color inversion true .

@nnuel
Copy link

nnuel commented Dec 14, 2021

After enabling, or setting the prop for multi-window to true, I get the same issue. However, setting it back to false again, doesn't solve the issue. The apps have prior to this only opened in fullscreen (minus the KDE plasma taskbar).

I did get the apps to display after reinstalling and re-initializing waydroid, so that's the only way to 'fix' it for now. And not bother with this setting.

@haru02w
Copy link

haru02w commented Feb 9, 2023

After 2 years, I'm having this same problem. When I run "waydroid prop set persist.waydroid.multi_windows true" and restart the container, nothing show up anymore.
Setting back to false works though.

@pesader
Copy link

pesader commented Apr 25, 2023

I believe I have the same issue, but I don't have invert colors enabled. When I launch an Waydroid app, I briefly get a transparent window saying "Phone is starting" then it disappears and the app doesn't show up.

waydroid_multiwindow_bug_compressed.mp4

Here are the logs I got running waydroid log:

Logs
(000796) [09:00:05] % umount /var/lib/waydroid/rootfs/vendor
(000796) [09:00:05] % umount /var/lib/waydroid/rootfs
(000796) [09:00:05] % umount /var/lib/waydroid/rootfs
(003479) [09:00:05] Introspect error on :1.17:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected
(003479) [09:00:05] Executing introspect queue due to error
(000771) [09:00:26] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(000771) [09:00:26] % modprobe -q ashmem_linux
(000771) [09:00:26] % chmod 666 -R /dev/binder
(000771) [09:00:26] % chmod 666 -R /dev/vndbinder
(000771) [09:00:26] % chmod 666 -R /dev/hwbinder
(006005) [09:04:10] Starting waydroid session
(000771) [09:04:10] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start
vnic is waydroid0
success
(000771) [09:04:11] % chmod 777 -R /dev/dri
(000771) [09:04:11] % chmod 777 -R /dev/fb0
(000771) [09:04:11] % chmod 777 -R /dev/video13
(000771) [09:04:11] % chmod 777 -R /dev/video12
(000771) [09:04:11] % chmod 777 -R /dev/video11
(000771) [09:04:11] % chmod 777 -R /dev/video10
(000771) [09:04:11] % chmod 777 -R /dev/video9
(000771) [09:04:11] % chmod 777 -R /dev/video8
(000771) [09:04:11] % chmod 777 -R /dev/video7
(000771) [09:04:11] % chmod 777 -R /dev/video6
(000771) [09:04:11] % chmod 777 -R /dev/video5
(000771) [09:04:11] % chmod 777 -R /dev/video4
(000771) [09:04:11] % chmod 777 -R /dev/video3
(000771) [09:04:11] % chmod 777 -R /dev/video2
(000771) [09:04:11] % chmod 777 -R /dev/video1
(000771) [09:04:11] % chmod 777 -R /dev/video0
(000771) [09:04:11] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid
(000771) [09:04:11] % mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(000771) [09:04:11] % mount -t overlay -o context="system_u:object_r:waydroid_rootfs_t:s0",ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs
(000771) [09:04:11] % mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(000771) [09:04:11] % mount -t overlay -o context="system_u:object_r:waydroid_rootfs_t:s0",ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor
(000771) [09:04:11] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(000771) [09:04:11] Save config: /var/lib/waydroid/waydroid.cfg
(000771) [09:04:11] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(000771) [09:04:11] New background process: pid=6093, output=background
(000771) [09:04:11] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(006005) [09:04:26] waydroidusermonitor: Received transaction: 1
(006005) [09:04:26] Android with user 0 is ready
(000771) [09:04:56] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(000771) [09:04:56] % lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
lxc-start: waydroid: conf.c: run_buffer: 321 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 988 Failed to run lxc.hook.post-stop for container "waydroid"
(000771) [09:04:56] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(000771) [09:04:56] % /usr/lib/waydroid/data/scripts/waydroid-net.sh stop
vnic is waydroid0
(000771) [09:04:56] % umount /var/lib/waydroid/rootfs/vendor/waydroid.prop
(000771) [09:04:56] % umount /var/lib/waydroid/rootfs/vendor
(000771) [09:04:56] % umount /var/lib/waydroid/rootfs/vendor
(000771) [09:04:56] % umount /var/lib/waydroid/rootfs
(000771) [09:04:56] % umount /var/lib/waydroid/rootfs
(008184) [09:05:08] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(008184) [09:05:08] *** output passed to waydroid stdout, not to this log ***

@PhilDevProg
Copy link
Author

@pesader Could you try running the same command again in a different terminal tab (don't stop the current command)? And does running waydroid show-full-ui work correctly?

@pesader
Copy link

pesader commented Apr 25, 2023

Could you try running the same command again in a different terminal tab (don't stop the current command)?

@PhilDevProg, sure! If I run waydroid app launch com.android.contacts in another terminal tab, I get:

[10:43:45] Sending reply failed

And does running waydroid show-full-ui work correctly?

It starts, then it crashes, then it starts again, then it crashes, and so on.

waydroid_multiwindow_bug_full_ui_compressed.mp4

Here are the logs again:

Logs
vnic is waydroid0
(000789) [10:48:32] % umount /var/lib/waydroid/rootfs/vendor/waydroid.prop
(000789) [10:48:32] % umount /var/lib/waydroid/rootfs/vendor
(000789) [10:48:32] % umount /var/lib/waydroid/rootfs/vendor
(000789) [10:48:32] % umount /var/lib/waydroid/rootfs
(000789) [10:48:32] % umount /var/lib/waydroid/rootfs
(014187) [10:48:48] Starting waydroid session
(000789) [10:48:48] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start
vnic is waydroid0
Warning: ZONE_ALREADY_SET: 'waydroid0' already bound to 'trusted'
success
(000789) [10:48:48] % chmod 777 -R /dev/dri
(000789) [10:48:48] % chmod 777 -R /dev/fb0
(000789) [10:48:48] % chmod 777 -R /dev/video13
(000789) [10:48:48] % chmod 777 -R /dev/video12
(000789) [10:48:48] % chmod 777 -R /dev/video11
(000789) [10:48:48] % chmod 777 -R /dev/video10
(000789) [10:48:48] % chmod 777 -R /dev/video9
(000789) [10:48:48] % chmod 777 -R /dev/video8
(000789) [10:48:48] % chmod 777 -R /dev/video7
(000789) [10:48:48] % chmod 777 -R /dev/video6
(000789) [10:48:48] % chmod 777 -R /dev/video5
(000789) [10:48:48] % chmod 777 -R /dev/video4
(000789) [10:48:48] % chmod 777 -R /dev/video3
(000789) [10:48:48] % chmod 777 -R /dev/video2
(000789) [10:48:48] % chmod 777 -R /dev/video1
(000789) [10:48:48] % chmod 777 -R /dev/video0
(000789) [10:48:48] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid
(000789) [10:48:48] % mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(000789) [10:48:48] % mount -t overlay -o context="system_u:object_r:waydroid_rootfs_t:s0",ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs
(000789) [10:48:48] % mount -o context="system_u:object_r:waydroid_rootfs_t:s0",ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(000789) [10:48:48] % mount -t overlay -o context="system_u:object_r:waydroid_rootfs_t:s0",ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor
(000789) [10:48:48] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(000789) [10:48:48] Save config: /var/lib/waydroid/waydroid.cfg
(000789) [10:48:48] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(000789) [10:48:48] New background process: pid=14261, output=background
(000789) [10:48:48] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(014187) [10:49:03] waydroidusermonitor: Received transaction: 1
(014187) [10:49:03] Android with user 0 is ready
(014187) [10:49:19] waydroidusermonitor: Received transaction: 1
(014187) [10:49:19] Android with user 0 is ready
(014187) [10:51:26] waydroidusermonitor: Received transaction: 1
(014187) [10:51:26] Android with user 0 is ready
(000789) [10:51:32] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(000789) [10:51:32] % lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
lxc-start: waydroid: conf.c: run_buffer: 321 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 988 Failed to run lxc.hook.post-stop for container "waydroid"
(000789) [10:51:33] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(000789) [10:51:33] % /usr/lib/waydroid/data/scripts/waydroid-net.sh stop
vnic is waydroid0
(000789) [10:51:33] % umount /var/lib/waydroid/rootfs/vendor/waydroid.prop
(000789) [10:51:33] % umount /var/lib/waydroid/rootfs/vendor
(000789) [10:51:33] % umount /var/lib/waydroid/rootfs/vendor
(000789) [10:51:33] % umount /var/lib/waydroid/rootfs
(000789) [10:51:33] % umount /var/lib/waydroid/rootfs
(019064) [10:52:17] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(019064) [10:52:17] *** output passed to waydroid stdout, not to this log ***

@PhilDevProg
Copy link
Author

It starts, then it crashes, then it starts again, then it crashes, and so on.

Does that happen with Multi-Window mode disabled too?

@pesader
Copy link

pesader commented Apr 25, 2023

Does that happen with Multi-Window mode disabled too?

No, this only happend with multi-window mode enabled. If I disable that, Waydroid works perfectly.

@PhilDevProg
Copy link
Author

Does that happen with Multi-Window mode disabled too?

No, this only happend with multi-window mode enabled. If I disable that, Waydroid works perfectly.

Then your issue is most likely this: #862

@pesader
Copy link

pesader commented Apr 25, 2023

Yes, you're right! I didn't see that issue, sorry for taking your time 😅

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

No branches or pull requests

8 participants