@lduboeuf , thank you. Unfortunately for me it appears after phone and/or waydroid reboot. I think I even uninstalled waydroid via helper (due to other problems) and it did remain.

You might be best asking here https://t.me/waydroidonut Please remember Waydroid is not a perfect solution to running android apps on UT and you need to set the correct permissions when setting up WayDroid for the apps that can to work correctly have a look through the post here https://forums.ubports.com/topic/5907/open-ubuntu-touch-to-all-android-applications/99 Also WayDroid is not a part of the UT OS, it is a separate project aimed at making it possible for those that want to use android apps.

Nevermind, it worked for few times. Now even with wifi disabled, my system still crashes so has to be something else cause it also.

@jmlich said in Waydroid infos needed : @wgarcia Acctually, I don't use any android applications, but waydroid sound like a way to bypass gap until native applications are written. There is usually one or two apps which locks people to android. In that case UT works well, but some people think they can keep both an Android phone and a UT phone with Waydroid, which is not the case.

@StephPTi Thanks, that looks just what I need, ill try it out today.

@WillemHexspoor i also have the same issue on Xenial on my Poco x3 NFC

@triguy said in How can I share files from my Ubuntu Touch host with Waydroid?: on my Google Pixel 3a, outside of the home, back, app switcher buttons being out of reach For others on Google Pixel 3a, this worked for me to get the back, home, and switch button raised up a bit so they could be accessed: waydroid prop set persist.waydroid.height_padding 100 See documentation here

@treebeard thanks @Kjetil

@WillemHexspoor Then I don't know the answer to your question, as I don't use waydroid.

@Chan1234 i had the same problem, maybe its because its only 32bit, and the image that it downloads is for a 64bit device

@EvilHare said in Launching waydroid shell on Redmi Note 9 Pro: @arubislander Ah, well then ok. I just thought there was a problem with my device or something I was doing wrong. I solved the problem for myself. I connected via adb to my device using the instructions: https://docs.ubports.com/ru/latest/userguide/advanceduse/adb.html. Then, inside the device, I launched the waydroid shell without any problems