The main thing here is that Ubuntu Touch doesn't have the latest and greatest support for Wayland/XWayland. This is needed so you can run traditional desktop apps. It will come in the future and there are already works on it on the desktop side of things. However, even with that, we can't expect for these desktop apps to magically work well on small screens with touch input. As mentioned, uWolf is in the OpenStore which is Librewolf but made to work better on phones. It still has some quirks though, caused by the same thing I mentioned earlier. It has no clipboard support and the performance isn't as good as the native browser.

@XPran As an addition to TELEports and Whatsweb, did you try as well to install Waydroid in Ubuntu touch? Native Whatsweb and TelePorts app for Ubuntu touch should do the trick for most day-to-day needs, and offer notifications. But having a fallback to official Whatsapp and Telegram in Waydroid may be usefull as a complementary solution, if you need some advanced features at some point.

@mihael Great thank you very much!

@Vlad-Nirky Ok, good ideas, thank you for your help.

@UBportsNews First of all, a huge thank you to those who contribute to the development of UT, its community, and the porting of new devices. You are exceptional! Would it be possible, as Felix and Sander started to do, to create sessions, webinars, or videos to explain application development under UT? How to get started and also progress in application or UT development, how to deal with the changes linked to Noble release, with the futur use of QT6, and so one. Thanks for reading. Vlad

@lduboeuf hey no worries, people work on this on their free time and I value and respect that. I'm happy something like this exists.

@Gabriel.de Run YouTube for as long as you can or carry out some other screen intensive operation. This will heat the GPU/CPU and screen and may through up an issue. If it happens within 5 minutes, your hardware may be at fault. If it the issue takes a long while to manifest, it can be normal for the aging device. The battery can also affect this if it is weak or failing. The screen is usually the first part along with power button to be damaged through misuse, but is usually the last item to fail through normal use.

@Faby https://forums.ubports.com/topic/11452/some-shell-programs-are-missing-in-24.04-1

Done! https://gitlab.com/alaskalinuxuser/trolly/-/issues

@haagch on morph it worked for a while on focal, but they seemed to make an update that just breaks it rn. on uWolf its a question of how to get location working.

@pparent said in Taking the plunge: Three niggles remain: You loose end-to-end encryption Yes, that's a fair point. For that reason alone, a direct method would be preferrable.

@slowcyclist There is a bug report which I found later. This is supposed to be fixed now, however, it is not for me. Just sits with Server Stopped forever. I don't see how I can disable and restart the service if you can't get past "Server Stopped" to get to the menus. Seems a clean install of the app would likely fix it, but how? Is there some way to "purge" click packages; as in, remove all the configuration files when you remove them? I'm thinking it may just be easier to have a list of packages, find out how to backup my contacts, call history and messages then wipe clean? Is there some information on doing that? Maybe an app or something built into UT to do that would be nice.

@Luksus yes I tried that also recently phablet@ubuntu-phablet:~$ sudo su root@ubuntu-phablet:/home/phablet# waydroid init -s GAPPS [11:29:47] Already initialized root@ubuntu-phablet:/home/phablet# waydroid session start [11:29:57] ERROR: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message [11:29:57] See also: <https://github.com/waydroid> Run 'waydroid log' for details. root@ubuntu-phablet:/home/phablet# waydroid log STOPPED (004619) [01:26:45] waiting 8 seconds for container to start... (004619) [01:26:46] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:46] waiting 7 seconds for container to start... (004619) [01:26:47] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:47] waiting 6 seconds for container to start... (004619) [01:26:48] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:48] waiting 5 seconds for container to start... (004619) [01:26:49] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:49] waiting 4 seconds for container to start... (004619) [01:26:50] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:50] waiting 3 seconds for container to start... (004619) [01:26:51] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:51] waiting 2 seconds for container to start... (004619) [01:26:52] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (004619) [01:26:52] waiting 1 seconds for container to start... (004834) [01:26:53] org.freedesktop.DBus.Python.OSError: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/dbus/service.py", line 712, in _message_cb retval = candidate_method(self, *args, **keywords) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/waydroid/tools/actions/container_manager.py", line 35, in Start do_start(self.args, session) File "/usr/lib/waydroid/tools/actions/container_manager.py", line 193, in do_start helpers.lxc.start(args) File "/usr/lib/waydroid/tools/helpers/lxc.py", line 402, in start wait_for_running(args) File "/usr/lib/waydroid/tools/helpers/lxc.py", line 396, in wait_for_running raise OSError("container failed to start") OSError: container failed to start (004834) [01:26:53] OSError: container failed to start (009986) [11:29:47] Already initialized (010058) [11:29:57] ERROR: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message (010058) [11:29:57] See also: <https://github.com/waydroid> (010058) [11:29:57] Traceback (most recent call last): File "/usr/lib/waydroid/tools/__init__.py", line 70, in main actions.session_manager.start(args) File "/usr/lib/waydroid/tools/actions/session_manager.py", line 35, in start name = dbus.service.BusName("id.waydro.Session", dbus.SessionBus(), do_not_queue=True) ^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 209, in __new__ return Bus.__new__(cls, Bus.TYPE_SESSION, private=private, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 99, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/dbus/bus.py", line 120, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message (010121) [11:30:17] % tail -n 60 -F /var/lib/waydroid/waydroid.log (010121) [11:30:17] *** output passed to waydroid stdout, not to this log *** Still its not working these are the logs

Has nobody with Volla X23 has had any experience with Waydroid at 24.04-1.0? Greetings Charly

@ikoz [image: 1760205347903-5ce2605b-eb49-418b-ba83-03b46c94457d-image.png] Channel list is empty

@foxx This is getting very off topic, politics are not that related to the issue. I never said that you cannot use your camera, it just has to be interfaced through Halium. You can quickly make an app with Qt that captures frames from the camera, and maybe use the Qt Networking framework to broadcast.

@mr_growl Yeah, max RAM I have is 16GB, but on an ARM based computer. With this one, I would have to virtualize x64 which would have a knock on performance. The main x64 Linux computer has 8GB. Not ideal. Let's just say I have been on the market for a better computer for a while. Hahaha Let me see what I can work out. Thanks for the steps and the build!

Hi @Luksus. I never found the FF3 with UT to be quite snappy enough. The possibility of Waydroid on the FF5 is a major plus. It's disappointing that can't use the higher resolution or 2nd camera.