https://forums.ubports.com/topic/11532/signal-ut-signal-desktop-for-ubuntu-touch

@grenudi Well, some quick items about this: Lomiri (aka Unity8) has 15 years of development (>) Unity is developed by a professional and capable team of designer and UX experts. I don't know why random people get the idea that the desktop is designed to be «just different from X». Lomiri has its own language and design. Object of which are simple, intuitive and beatifull. Ubuntu Touch is not Android. Ubuntu users are used to Unity patterns. So, have them in Ubuntu Touch makes sense to us. (offtopic) Andoird UI is a mess, but the more time passes, the more it adopts Unity design language.

Thanks @danfro , that's a helpful hint to know.

@ToxyPoxy Although it seems that calls could possibly make its way to Whatsapp web one day, which would be amazing, and then we will probably be able to support it inside the app. https://beebom.com/whatsapp-web-voice-and-video-calling-coming-soon/ https://3dvf.com/en/whatsapp-will-soon-allow-making-calls-directly-from-your-web-browser/

@MrT10001 Hello, I don't complain. Everything else works great. It's a pity that these little things don't work, because if they did, UBports would have the best system on the market, and free as well. These last key strokes are the hardest to give.

Hi @Gabriel.de. That's great to hear. Welcome to the UBports forum.

@Lorenzo said in A few questions on redmi note 9: Are they treated as two separate devices or will they be rolled into one? Xiaomi devices are often wildly different from one another even if the model name and number are very close. Not sure about this one, but if they are separate devices now, they probably need to be and will stay that way.

@TheTrench You need to delve deeper into 5G and what 5G is, plus what Android version supports 5G on that device. 5G falls into two categories - 5G Non Stand Alone (NSA) and 5G (SA). 5G NSA piggybacks of the 4G LTE infrastructure end to end in simple terms. 5G SA is full 5G end to end. This can be affected by available networks, service providers, Android versions and vendor BLOBs and device hardware. You cannot expect newer firmware files to work on an older version of Android without issues or just not working. I bought a 5G device when 5G was in its infancy and always got 4G LTE indicated and 4G speeds. 5G has a better infrastructure now and it still shows 4G LTE in a lot of cases. My new device is 5G and always shows 5G and is a bit quicker, but not in all cases.

And here a little success story on combining the Clickable Snap & the Docker Snap, allowing to build AND test a click package directly on the device (in this case a JingPad). Photo courtesy of Sander: [image: 1762635258156-photo_2025-11-05_21-28-47-resized.jpg]

@fake-alex So what's the plan... are you offering to send these devices to people who want to try to make a port for them? Developers need to have the device in hands.

@RJDan Not while using encryption, because all the info needed for the functions you care about are inaccessible until after your home folder is decrypted.

New version is out Introducing protocol v2 - now client apps do not need to use the microphone, audio recording is performed on a server. There are some flaws for this decision, though. CPU load has been reduced in this release This release is also backwards compatible with protocol v1, where client sends recorded data to server, just in case someone wants to send audio data from other sources. Also, my apologies, I forgot to link Client library for v2 protocol Client library for v1 protocol (requires Microphone permission)

I still don't know how to make the sdcard appear directly on my desktop computer when I connect my phone, but I have a workaround : symlink the sdcard mount point in the /home/phablet directory ( = "internal storage" on the desktop computer). This is easily done using the terminal (or adb shell). Find the exact mount point of the sdcard using the command mount; it is something like /media/phablet/XXXX-YYYY. Then enter ln -s /media/phablet/XXXX-YYYY ~/sdcard

@xforze Hello while I have not yet unraveled all the intricacies of ubports gitlab build, here is what I have found so far. Binaries are uploaded to https://system-image.ubports.com like usual with Debian dirs, there are index directories and a huge pool dir containing all the data files in compressed form (tar.xz): https://system-image.ubports.com/pool/ data files beginning by 'rootfs-' are as the name implies a frozen file system with all deb packages data files beginning by 'device-' contain the android container data files beginning by 'boot-' are the ones of interest with 2 directories: partitions: boot.img and vendor_boot.img system: here is where can be found the kernel name, under system/usr/lib/modules ls 5.4.289-qgki-g4ddb22d91965 cd 5.4.289-qgki-g4ddb22d91965/ ls source source -> /builds/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/workdir/downloads/kernel-fairphone-qcm6490 note: this is a broken link, but it shows from where is coming the built archive. If you git clone the directory (note that in the Gitlab UI the directories appear to be called 'Halium 11' but if you copy the Url you get android 11 instead) git clone https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/kernel-fairphone-qcm6490 git branch -a halium-11.0 remotes/origin/HEAD -> origin/halium-11.0 remotes/origin/halium-11.0 remotes/origin/halium-11.0-rebase so there are 2 main branches, halium-11.0 and halium-11.0-rebase on halium-11.0-rebase branch, use git log and search for 5.4.289, you'll find commit cb5f77d16c36027aa197fc26183b8d7e17c8f016 by a lineageos developer. on halium-11.0 branch, you'll not find a commit containing the string 5.4.289, the most recent with 5.4. will be 5.4.219. So what I think at the moment is that when the built is done, the fairphone-5 dir is switched to the master branch and the deviceinfo file contains 'deviceinfo_kernel_source_branch="halium-11.0-rebase" I have not found where is hidden the procedure to build for 24.04. The .gitlab-ci.yml under the fairphone-5 directory seem to build for 20.04 in all branches. That's still mysterious for me. Still it seems clear that recent dev is happening in the hallium-11.rebase branch so it must be the one. Now, 'qgki' is clear: it stands for qualcomm generic kernel image'. The prize would be to find a relationship (if any) between 'g4ddb22d91965' and a specific commit in git. No idea currently

I can't edit my first post, so this is the UP TO DATE TUTORIAL : How to install UB T - Ubuntu Touch - UBPorts on a Poco X3 Pro - Vayu Unlock bootloader Install TWRP or OrangeFox Install a global MIUI 12.5.9 with Android 11 (to be sure all is ok) http://xmfirmwareupdater.com/miui/vayu/stable/V12.5.9.0.RJUMIXM/ Download Artefact on github : devel-flasable-focal (to see the last version is here Extract the zip Download the vendor from Droidian vayu 100 or take the last one here : Droidian git (it is the Sailfish one, and I don't find it on UBT) It is the MIUI with some fix for Linux on phone. You could try just the adaptation images, but not tested : Adaptation for Poco X3 Pro codename Vayu Extract the zip Reboot your phone in recovery Reboot in fastboot from recovery so it is fastbootd (Android fastboot, don't works) From the Ubuntu zip : Upload with fastbootd on phone boot.img as boot- From the Droidian zip : Upload with fastbootd on phone vendor.img as vendor, dtbo.img as dtbo, vbmeta.img as vbmeta on TWRP format data to remove encryption, and put ubuntu.img in data folder (/data). With MTP on TWRP for example (you copy it from you computer and you could find in /data/media. (It could need a reboot to recovery, after a format to see the media folder) Or with ADB : adb push ubuntu.img /data/ Reboot phone Enjoy ! The mic sound seem to be lower than Droidian, so a fix could be taken on Droidian. EDIT : Sorry, we don't have to flash system partition, UBT use the ubuntu.img in /data.

@Vlad-Nirky said in [Poco X3 pro] Need help system not flashing: @snailc said in Need help system not flashing: miui version: 12.5.6 On the device page only poco X3 is listed, i don't see poco x3 pro. https://devices.ubuntu-touch.io/ This device is different, maybe it can use UT... The miui 12.5.6 is Android 11 and the poco X3 is on halium 10 so need Android 10. You should ask on the Miatol Telegram page if somebody has already used this device... https://t.me/UTForMiatoll Hi ! X3 Pro is not on device page, because we don't have maintainer, maybe I will if UBT choose LVM and I could keep my other OS to. The port is very good but need few check. I agree with you, people with Miatoll can help and we have a global X3 Pro Linux group : https://t.me/LinuxForPocoX3Pro The tutorial page for X3 Pro : https://forums.ubports.com/topic/11334/poco-x3-pro-ubuntu-touch-tutorial-installation-guide-vayu-and-help-channel

woah, great work!

This is awesome! Can't wait for the future of Lomiri