@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.

Missing characters

@smobilesoft Well... I have the same phone. I am not a porter and I apologize to them (or invite them to correct me) for the shortcuts used. I have unlocked it, install the needed ROM to be compatible with UT port. The UT port interacts with an abstraction layer called Halium. There is a version of Halium for each version of Android 9, 10, 11, 12, etc. Halium interacts with the low-level Android drivers that are left in place when UT is installed and Android is replaced. The port therefore expects to have very specific drivers (those of the recommended version of Android). Each ROM contains a number of partitions that are either left in place, replaced, or modified. Altering these partitions (or using a non-compliant ROM that has other partitions) can therefore result in a system that cannot receive UT or anything else at all. You can experiment, and it may be beneficial to you and to others who are in the same situation or not. When the device is unlocked and the ROM joyeuse_global_images_V12.0.3.0.QJZMIXM is in place, installer can resize the needed partitions via [image: 1760128909183-bead290c-af62-4237-82e9-9d1ff28cf229-ut-install-checkbox.png] /home/jll/UBT/4Install/UT install checkbox.png

@mihael Great thank you very much!

@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!

@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.

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

@ola Now you can enjoy

@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.

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

@Eric-H Thank you for the MIUI 12.5.9 global link after installing this everything worked, what I was missing was that

Just a quick question: anyone knows if there is a particular difficulty to build Signal-desktop (Electron app) as a .click package? Because this would be a major addition to Ubuntu Touch. Knowing that Mobian have binaries and build scripts for ARM ( https://github.com/0mniteck/Signal-Desktop-Mobian ) (And after we could certainly tweak the interface to make it responsive, like it is done on whatsapp web which is a very similar interface.)

@Charly Snap doesn't make sense for these small standalone utilites. Also fdisk doesn't exist as snap and rsync packages are only some outdated third party programs, which I would never install.

I reinstalled the update with the UBports installer again, then restarted the phone twice for testing, and the restart duration was normal. It looks to me like everything is working as expected now.

@pparent In the real world, I'd be happy about any native Signal app for UT, be it secondary, primary or both.

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

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

@MrT10001 hi @MrT10001, I managed to install the system by doing it this way, based on the instructions from a post on the forum. This might help other people. Thanks for your help Video to enter Fastboot mode in order to unlock the bootloader: www.youtube.com/watch?v=cUOf0sF2RU4 Forum for commands to unlock the bootloader: forums.ubports.com/topic/10690/tb-x306f-3-gb-32-gb-android-11

@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