@messayisto At this time Fairphone 5 port is more mature than Volla Phones Quintus port who itself is more mature than Brax3 port : https://devices.ubuntu-touch.io/ However, if you want multiboot, Quintus is to be preferred. If you need VoLTE today, You'll need to check in details.

@fredldotme Hello Alfred. Excellent news! Thank you for this improvement (at least it is for Waydroid users ) Regards

@gpatel-fr said in Status of the Location Service (GPS, A-GPS, GLONASS, BeiDou, Galileo) ?: See an analysis here: https://ti.qianxin.com/blog/articles/Analysis-of-the-Hidden-Backdoor-Event-in-Qualcomm-GPS-Service-EN/ TLDR: backdoor is too strong a word, but there are privacies issues. If the software is rewritten as open source, this could be less problematic. Thanks for all these details about the AGPS privacy issue, I understand the idea behind this. It seems it's hard to have a good signal when the phone is inside a car (all satellites were red in GPSTest). I think I need another device as navigating system for my car. I'll check next days if my device could have locaiton fix with Glonass, Beidou and Galileo satellites. I expect using more data sources should improve measurment quality, isn't it ?

@pparent Amazing improvements, thank you very much!

@mr_growl Hope you had a great vacation!

Ah thank you. This seems to have been set to tethering. I wasn't aware this would also stop file transfers when I've been looking to diagnose why. Resolved

@mafman97 You can install Windows to a USB thumb drive and run MSMtool from that There is also a linux method somewhere in the OP 5 or 6 forums, but results are variable.

Had a bit of time playing with this. Looks like when i add the needed luser+pass UT borks the config. After import but before edit in gui: root@ubuntu-phablet:/home/phablet/Documents/vpn# cat /etc/netplan/90-NM-52d84ad9-6e22-45a6-b0cc-77e6639f57dc.yaml network: version: 2 nm-devices: NM-52d84ad9-6e22-45a6-b0cc-77e6639f57dc: renderer: NetworkManager networkmanager: uuid: "52d84ad9-6e22-45a6-b0cc-77e6639f57dc" name: "main-vpn" passthrough: connection.type: "vpn" vpn.ca: "/home/phablet/Documents/vpn/server.crt" vpn.cert: "/home/phablet/Documents/vpn/phone.crt" vpn.connection-type: "password-tls" vpn.dev: "tun" vpn.dev-type: "tun" vpn.key: "/home/phablet/Documents/vpn/phone.key" vpn.password-flags: "1" vpn.port: "<port>" vpn.remote: "<domain>" vpn.tls-crypt: "/home/phablet/Documents/vpn/tls.key" vpn.tls-version-min: "1.3" vpn.tls-version-min-or-highest: "yes" vpn.tun-ipv6: "yes" vpn.service-type: "org.freedesktop.NetworkManager.openvpn" ipv4.method: "auto" ipv6.addr-gen-mode: "default" ipv6.method: "auto" proxy._: "" After adding user+pass: root@ubuntu-phablet:/home/phablet/Documents/vpn# cat /etc/netplan/90-NM-52d84ad9-6e22-45a6-b0cc-77e6639f57dc.yaml network: version: 2 nm-devices: NM-52d84ad9-6e22-45a6-b0cc-77e6639f57dc: renderer: NetworkManager networkmanager: uuid: "52d84ad9-6e22-45a6-b0cc-77e6639f57dc" name: "main-vpn" passthrough: connection.type: "vpn" vpn.ca: "/home/phablet/Documents/vpn/server.crt" vpn.cert: "/home/phablet/Documents/vpn/phone.crt" vpn.cert-pass-flags: "1" vpn.connection-type: "password-tls" vpn.dev: "tun" vpn.dev-type: "tun" vpn.key: "/home/phablet/Documents/vpn/phone.key" vpn.password-flags: "1" vpn.port: "<port>" vpn.remote: "<domain>" vpn.username: "phone" vpn.service-type: "org.freedesktop.NetworkManager.openvpn" ipv4.method: "auto" ipv6.addr-gen-mode: "default" ipv6.method: "auto" proxy._: "" Emtyied the file then inserted the origynal config, reboot, then trying to connect with nmcli: phablet@ubuntu-phablet:~$ sudo su - [sudo] password for phablet: root@ubuntu-phablet:~# nano /etc/netplan/90-NM-52d84ad9-6e22-45a6-b0cc-77e6639f57dc.yaml root@ubuntu-phablet:~# nmcli con up id main-vpn --ask A password is required to connect to 'main-vpn'. Password (vpn.secrets.password): •••••••••• Error: Connection activation failed: The VPN service stopped unexpectedly Hint: use 'journalctl -xe NM_CONNECTION=52d84ad9-6e22-45a6-b0cc-77e6639f57dc + NM_DEVICE=ril_0' to get more details. Output from yournalctl from the last line: Nov 03 19:44:41 ubuntu-phablet NetworkManager[1855]: <info> [1762195481.3645] manager: (ril_0): new Broadband device (/org/freedesktop/NetworkManager/Devices/8) Nov 03 19:44:41 ubuntu-phablet NetworkManager[1855]: <info> [1762195481.3696] device (ril_0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 03 19:44:41 ubuntu-phablet NetworkManager[1855]: <info> [1762195481.3704] device (ril_0): modem state 'initializing' Nov 03 19:45:22 ubuntu-phablet NetworkManager[1855]: <info> [1762195522.7025] device (ril_0): state change: unavailable -> disconnected (reason 'modem-available', sys-iface-state: 'managed') Nov 03 19:45:22 ubuntu-phablet NetworkManager[1855]: <info> [1762195522.7151] device (ril_0): Activation: starting connection 'Vodafone HU' (45cef972-7709-52f9-90a2-6b67d193ddf6) Nov 03 19:45:22 ubuntu-phablet NetworkManager[1855]: <info> [1762195522.7154] device (ril_0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.3959] device (ril_0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.4014] device (ril_0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <warn> [1762195523.4075] device (ril_0): retrieving IP configuration failed: modem IP method unsupported Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.4530] device (ril_0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.5092] device (ril_0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.5101] device (ril_0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 03 19:45:23 ubuntu-phablet NetworkManager[1855]: <info> [1762195523.5122] device (ril_0): Activation: successful, device activated. Nov 03 19:46:05 ubuntu-phablet NetworkManager[1855]: <info> [1762195565.5396] vpn[0x55b0078e60,52d84ad9-6e22-45a6-b0cc-77e6639f57dc,"main-vpn"]: starting openvpn Not much, lets see what journalctl -e had to offer: Nov 03 19:54:14 ubuntu-phablet NetworkManager[1855]: <info> [1762196054.8404] agent-manager: agent[75085e56325963a9,:1.110/nmcli-connect/0]: agent registered Nov 03 19:54:14 ubuntu-phablet NetworkManager[1855]: <info> [1762196054.8451] vpn[0x55b0071c60,52d84ad9-6e22-45a6-b0cc-77e6639f57dc,"main-vpn"]: starting openvpn Nov 03 19:54:14 ubuntu-phablet NetworkManager[1855]: <info> [1762196054.8475] audit: op="connection-activate" uuid="52d84ad9-6e22-45a6-b0cc-77e6639f57dc" name="main-vpn" pid=5266 uid=0 result="success" Nov 03 19:54:19 ubuntu-phablet NetworkManager[5278]: 2025-11-03 19:54:19 Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore. Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: Note: --cipher is not set. OpenVPN versions before 2.5 defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback ple> Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: WARNING: file '/home/phablet/Documents/vpn/phone.key' is group or others accessible Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: OpenVPN 2.6.14 aarch64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: library versions: OpenSSL 3.0.13 30 Jan 2024, LZO 2.10 Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: DCO version: N/A Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: Insufficient key material or header text not found in file '[[INLINE]]' (0/128/256 bytes found/min/max) Nov 03 19:54:19 ubuntu-phablet nm-openvpn[5278]: Exiting due to fatal error Nov 03 19:54:19 ubuntu-phablet NetworkManager[1855]: <warn> [1762196059.3200] vpn[0x55b0071c60,52d84ad9-6e22-45a6-b0cc-77e6639f57dc,"main-vpn"]: dbus: failure: connect-failed (1) Nov 03 19:54:19 ubuntu-phablet NetworkManager[1855]: <warn> [1762196059.3222] vpn[0x55b0071c60,52d84ad9-6e22-45a6-b0cc-77e6639f57dc,"main-vpn"]: dbus: failure: connect-failed (1) Nov 03 19:54:19 ubuntu-phablet lomiri-indicator-network-service[4655]: Debug: VPN Connection Failed "The VPN connection 'main-vpn' failed." ((null):0, (null)) Nov 03 19:54:19 ubuntu-phablet lomiri-indicator-network-service[4655]: Debug: VPN Connection Failed "The VPN connection 'main-vpn' failed because the VPN service stopped unexpectedly." ((null):0, (null)) Im out of ideas at this point.....

@pparent I tried it at gps.coordinates.net with Morph and it got to the next street from mine so it seems to work. This is with 24.04 RC on a Fairphone 5.

@itsjusthim Thanks for trying. The kernel misses the telephony support, which causes the imei not showing up. I only own the F model, so I cannot help with this. (n case you would like to try yourself, replace akita_row_wifi with akita_row_call in the deviceinfo file, and in all overlay files, and build the all img files. This will enable the missing kernel support, but more might be missing.) I am still working on the grahics issues.

@pparent An issue has been created at https://github.com/rinigus/pure-maps/issues/720 I am confident that the problem will be resolved.

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

said in Orange screen crash on Vollaphone 22 / Noble 24.04: Seems to stop happening when I disable emergency notifications. Actually it happened again. It seems to happen when I'm in a specific place, and connected to a specific Wifi network. I will avoid connecting to that network to see if it's better.

Hello forum, So I have the impression that volte cannot yet be used reliably on my phone. I have therefore disabled it and am waiting for further progress. What is still unclear to me is what the situation is with VoWLAN or VoWIFI? Many greetings Charly

Read the porters notes here. It looks like you have the T-Mobile version of the N100. You need to upgrade/downgrade to the stipulated firmware used by the porter. Here is a similar story.

@MrT10001 Me and another person here on the forum tried upgrading Sony Xperia X from focal to noble, but failed. It is stuck on the bootlogo and one of the devs or porters wrote that they are still investigating in it. So the Sony Xperia X is on the list of non upgrded devices.

@Vlad-Nirky Here it is: https://pixeldrain.com/u/u4qB51S8