@RapidRotator How did you install Waydroid and the Waydroid image? I installed it via Waydroid Helper (regular image, not Gapps), and everything just worked. Had to grant a few random permissions to microG, but everything else including signature spoofing was supported out of the box. Edit: I should also mention that I did nothing special to install microG. Just downloaded the regular APK (NOT the user mode one), and installed it. Then updated via f-droid.

@fredldotme Nice, though I just logged in to say that I can't test it anytime around. I've lost the phone. It's been a few days so I have no hope getting it back by a chance. I've been thinking in the meantime and decided I'll rather not buy another one anytime soon. I'm still interested in using Ubuntu touch but there are points to address before I'd be happy with it, so I might try to help solving them in VM (or just wait if eventually these got solved...). For now I've set price alerts in my favorite shops, hoping to catch next nice discount

Hi Zaito, so sorry for delay, I have only just logged on in ages. I tested it on GS5 only - installed UT 24.04 because it was the only way to make phonecalls when 3g packed up. Nothing I did enabled Waydroid to persist. Meaning that if waydroid was closed for any reason, you couldn't reboot it without a completely fresh installation. This rectified in June with a new UT update. Everything works well in both UT and Waydroid with one exception; there is no clipboard on waydroid. Which means you cannot copy or paste anything in any circumstances. If I need waydroid copy facilities I have to use another phone running UT20.04. Hope all is well.

@bestenaizena Because you need to "ask a question" before. Then you will be able to mark it solved directly or by choosing a post as the solution.

@O.o. said in Can I change how Waydroid works?: I'm trying to get away from Android, and what I end up doing is running Android in a UT sandbox to get the apps I need going. True, but that's the same whether or not you can see the sandbox. Personally I see Waydroid as a crutch. It's better not to need it, but it's there if you do. And if you only run Waydroid every now and then, as many of us do then most of the time you are effectively not using any kind of Android.

@Vlad-Nirky Hello, thank you for this information. Of course it's stupid for me, but it makes things clear! My two most important apps establish data connections to devices via Bluetooth. It's about solar and LFP batteries I can probably forget that now. Have a nice evening & best regards Charly

@RJDan Same here. As of now I have registered my Waydroid container as a dev device just to get Swedish bankID or Banking apps to work. Never really got MicroG to work

Ok, this was what I didnt understand, that I have to install Molly in the waydroid container. Done! Thanks a lot for helping me! Now I can (nearly*) leave the android universe and move to Ubuntu touch. *"nearly" because of the waydroid container

I've installed "Waydroid files" app and Can access the files (runs well under 24.04)

I found a solution: The private DNS must be disabled, and the network connection needs to be restarted.

Since Waydroid is using Linage you can still limit what the apps and services in the Android OS, such as Google Services, can access. Ive also noticed that both F-droid and Play Store auto updates when Waydroid is running, however they can lock up when booting Waydroid freshly since they seem to complain about time not being correct. I might be forced to use waydroid since my country have apps I need that only exists on iOS or Android. So this Topic is very relevant for me as in needing setup waydroid and make it a dev device since Waydroid is not certified ( Waydroid: Google Play Certification )

Someone actually has a weird discovery. You can copy paste between Waydroid and Mimi browser. You can't even do it anymore inside Waydroid since A13 No one knows yet why that is the case. It won't help with accessing clipboard from and to Waydroid though since Mimi browser also can't access system clipboard but perhaps something to look at

@gandalf Same echo problem for me.

@AmauryDBZ I have no idea. I dont have time right now to test it.

A puzzling issue is that when I see the prompt 'waydroid is stopped' in the UT command line, Waydroid is actually running, and operations within its system GUI appear to be functioning normally.

@wolfgang1 Have you checked the Autheticator apps from the OpenStore? Maybe you can migrate to them? But I assume the one you're using is online and synced so probably more complicated. In any case, Waydroid's image is separate from the UT updates. Waydroid has its own updater. If a UT update includes a new version of Waydroid, that would only be the binary and not the Android image that you already initiated and configured. Best practice is to not update both UT and Waydroid while away from a machine that you can use to get back to working state in case something breaks