Just an update, I gave up on trying the KDEConnect workaround. I did some deep investigation on resolving the issue within Waydroid itself, and documented my progress. It's definitely a feature-request in Waydroid. https://github.com/waydroid/waydroid/issues/211 I haven't done any more work on it for a while, since my last post on github. There are a few libs being used in Waydroid, which I linked to, which have sparse documentation. I don't have deep enough knowledge of these languages and platforms to be able to fix this easily - not to mention android's workflow for builds. Wasn't able to do a build of LineageOS on my PC; some incompatibility with package versions. It'd be nice to resolve this for everybody who uses Waydroid, but IRL is taking priority for now.

I also have an x23 and ran into all that. I worked the issue to a halium mismatch. The Waydroid Helper app uses v13 and the base install covers up to v11 and guess where our phone sits. Its v12. So eventually I'll dive into it and probably just end up building an x23 specific version which I'll drop in here and on GitHub. I have no clue when I'll get to it though, I have like 5 other major projects from custom kernels, a few apps, a homelab server to finish, and getting my volla to run android apps. But don't worry some of us are hammering this issue out.

@Sheihorath Thankss, marking as solved

Hi @bamboy360 I see you made quite some posts here. I appreciate your enthusiasm for Ubuntu Touch and your intention to help however you can. I just wanted to clarify that the forum is intended to discuss topics with the community. I'm explaining this because some posts can be interpreted as bug reports or feature requests. For bugs and requests it's best to create an issue on Gitlab or to the relevant project (Waydroid or a specific app). Cheers mate

@Moem No problem. There's bits and pieces of information scattered around, so sometimes it's hard to learn about these things.

Hi @Ken1971 The easiest way is to use SSH in my humble opinion.

@naizena I noticed that too! Very nice. :thumbs_up_light_skin_tone:

@ds2k5 said in Signal stop working after switch backup Ubuntu and back zu Signal: How to setup if close the App that the app will closed that I do not need to do it by hand Getting Waydroid apps to work more like regular UT apps is still a work-in-progress. For now you probably have to use the work-around you discovered.

@Caedem or you can set up some shared folders, in orddder to exchange files. I did it following this guide: https://docs.waydro.id/faq/setting-up-a-shared-folder The only drawback is that you have to do it every time you torn on the device.

@arubislander Reinstalled Waydroid + Fortitoken, and got new key from our IT folks and now it connects again. Not clear though whether a glitch with the server (resulting in an unacceptable level of failed logins) or an OTA-5/Waydroid problem was the root cause.

@Luksus so there's an unofficial app that works. Fantastic! I'm receiving my Nexus 3a in two weeks but I have a Suunto watch though, which only supports Android and IOS (no web app)

@MrMonstache You may get a quicker answer here https://t.me/waydroidonut

Nice, that is good news for F-Droid enthousiasts and enthousiasts of open-source app stores serving similar function to the Google Play store which contains only free and open source apps.

Hi @linuxfanche From what I understand from this video, they are using the DisplayLink technology via an app from the Google Store. I doubt there is something cooked in Ubuntu Touch to take advantage of DisplayLink. But when it comes to possibilities, this give me hope that with enough work it can be achieved: https://en.wikipedia.org/wiki/DisplayLink#Linux As for the waydroid part of your question, I also doubt the necessary connection are available for the DisplayLink app to work as intended. Best try it out to be sure :man_shrugging: My best