Black screen of death w/ waydroid
-
i have a problem when using waydroid and ubuntu touch on fairphone 5. im running android 13 with version 24.04-1.1 stable
a problem i come across a lot is keeping waydroid (full application open) on and then setting my phone down to do something. my ubuntu touch device goes to sleep and then when i go to try and turn the screen on, it doesnt turn on. i then try tapping the device only to hear the tapping sound of the buttons but still nothing.
right now the only way out of this is by holding the power button and the volume down button to reboot the phone. This is massively frustrating, does anyone have a solution to this? i really want my waydroid phone to be on and not have it crash my entire linux phone's screen when it goes to rest or when ubuntu itself rest.
-
Hello,
don't seem to be a general problem since with my config I can't repro it; after my phone goes to sleep, when I press the power button the screen lights on and I get the lock screen and after unlocking, waydroid is exactly where it was before (I tested with the android camera app)
You may need to give more specific steps for others to see the problem.
-
@gpatel-fr yes, you have to leave it for about 10-15 minutes for the system to idle. once its idle, it will not allow the blank screen to come back up to a login screen or anything honestly. also just stay on the waydroid home screen and either let it go black Or turn the screen off yourself for 10-15 mins. Im not sure whats causing this on my phone. the key part is to keep the waydriod homescreen as the main active app and dont switch off of it
thanks for responding
-
I tried to follow this way this morning: started the phone, launched Waydroid, waiting on the Waydroid home screen for 15' for the FP5 to go black, then wait 15' more and pressing the power button: the phone was back to the lock screen and after that Waydroid was operational. I have 24.04.1 stable installed over Android 13 like you.
-
I may have to eat my words here. After doing the test as described in my previous post, I just stopped Waydroid, stuck the phone in my pocket and got out.
Several hours later, I wanted to use my phone and had an experience that looks like what you said, but a bit different: I could vaguely see the lock screen but as seen behind a very dark screen, and I did not succeed in unlock the screen. After fiddling for about a minute trying to bring the phone to life, it did go darker still, I could not even see anything. I restarted the phone and it worked as normal, so it was not a case of battery gone to nothing.
I did not relate immediately this problem to your post because it was slightly different - I had Waydroid stopped. But now that I think of it, maybe it was. If it's true, starting Waydroid and letting the phone go to sleep could have unexpected, long delayed consequences. If I had not seen it before, maybe it's because I almost never use Waydroid.
-
G gpatel-fr referenced this topic
-
said in Black screen of death w/ waydroid:
I just stopped Waydroid,
Or so I believed at the time. However, when I start the phone and I run
ps fauxww | grep way
I get nothing. When I start waydroid and after running the so-called 'waydroid stop' app, when I run the same command line I see a line with the waydroid container still present. So the 'waydroid stop' app does not in fact stop waydroid, and while I was naively believing it was removed from memory it was still running.
And while repeating the test this morning I still got to the unlock screen and could use the phone, I noticed that the screen was darker than normal, as if the phone was remembering it was half asleep still
-
@gpatel-fr Sorry it took So long for me to get back to you, i thought i had a simple fix where i would just put waydroid as a background app and leave a native UT app in the foreground. this worked for a while until i tried to get microg working on waydroid. The problem i think we are having is waydroid not releasing the screen and keeping the screen off if we were to turn the screen off while waydroid is active and let it rest for a while this will happen. Another thing is this seems to come up whenever i use Signal, normal resting and its fine. im not sure whats going on but it seems there some incompatibility with waydroid and Ubuntu touch when idling or sleep mode.
this hurts compatibility for me because i would love to have my waydroid running while my screen is off as i can get notifications and such. What do you think or would recommend as an alternative to waydroid? especially for android apps? Not running Waydroid and just getting a seperate device for that? this is troubling
-
@gpatel-fr oh yeah that waydroid stop app thing doesn't work lol, i found that out awhile ago. running the commands like waydroid stop definitely doesnt work. so i resort to killing the Pid