@mr_growl Hope you had a great vacation!

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

@wilson101 OK sure do as you prefer! The last thing I can say is that normally you must have the compiled module in your application in qml-plugins/Pparent/Notifications/libNotificationsPlugin.so and qml-plugins/Pparent/Notifications/qmldir Then you can include the qml module dir in c++ with QQmlApplicationEngine engine; engine.addImportPath("qml-plugins"); That's all I can say! I wish you good luck!

@Carlos said in Call for testing: Ubuntu Touch 24.04-1.1: This weekend I updated my Vollaphone22 from 24.04-1.0 to 24.04-1.1 and screen starts blinking on boot before the logo Ubuntu appears. With installer reinstalled 24.04-1.1 without wiping data and everything I use every day starts working normally until I found a serious bug on calls. Yesterday a friend calls me, I answered the call but no sound from other side. My friend repeated calling me and all answering was no sound. With other phone at hand I search the source of the error and found the Vollaphone22 was the culprit. How to reproduce is like this, make a call to other phone, wait that the other side answer the call, talk to test that audio is ok, wait that the other phone hang the call, now if you repeat process there is no sound if answered the call. Only rebooting Vollaphone works again, untill other phone terminates the call first and error returns. This error does not happens on version 20.04 stable. Thank you for the report. We're looking into this issue and will delay Ubuntu Touch 24.04-1.1 until we have this issue figure out. @mjosenhans said in Call for testing: Ubuntu Touch 24.04-1.1: I yesterday installed on my volla phone 22 Ubport 24.04-1.1 RC1 via RC channel. I had problems with incoming and outgoing voice calls without any voice being heard in both directions. Thus I reinstalled 24.04-1.x stable via stable channel. However instead of running the again the 24.04.1 software from stable, the phone is now in a reset loop. It shows the volla screen, then a black screen via backlight on, then a black screen with backling off and then again the volla screen. And so on. When going into boot loader, I was able to start the recovery mode, however it did not change, it is still in boot loop. Ubports installer is not finding the phone too. What can I do? I plan tomorrow to go to the phone service shop in berlin, which provides volla service and try to reflash the phone. We're sorry that this happen. Please try the following: Boot to bootloader by pressing Volume Up + Power (or Volume Up + plugging cable), then select "Enter fastboot menu". Do not enter recovery. Starts UBports Installer, then manually select "Volla Phone 22" (the Installer currently cannot auto-detect device model in bootloader mode). Select "24.04-1.x Stable" channel and ensure "Bootstrap" option is checked. Leave "Wipe Userdata" unchecked. Follow further instructions from the Installer.

@pparent Amazing improvements, thank you very much!

@XPran You need to turn off the phone, and then boot with long push on "power" and "volume up" buttons at the same time, until you see a "Recovery Menu", then select the first option "Boot recovery", then connect it in USB to your computer and the installer should work fine. Select Ubuntu Touch 24.04, and sit back & relax while the installer is doing its job.

I've been having some issues using Libertine running apps and searched the forum. It seems some others are also having issues setting up a proper Libertine container on the Google Pixel 3a. I'm placing a link to here. https://forums.ubports.com/topic/11232/unable-to-create-libertine-container

@UBportsNews Firstly thanks to the community, Ubuntu Touch on my Fairphone 4 on 24.04-1.1 RC1 is awesome! I would like to ask regarding the future of Ubuntu Touch, is it planned to move away from a Ubuntu base and move to something like Debian for example? If not, what are the advantages of a Ubuntu base?

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

@pparent Waydroid and libertine aren't app distribution channels and snaps are just terrible (and centralized with a proprietary backend). Maybe if there was proper Flatpak support in UT, but that still wouldn't give us click-packages.

I've made a new pull request: https://github.com/alefnode/ubports-apps/pull/59 Anyone who would like to join the testing is welcome!

I've succeeded in making a .click package, here is the topic for the app development: https://forums.ubports.com/topic/11532/signal-ut-signal-desktop-for-ubuntu-touch

@sixwheeledbeast To use UT, you must never relock the bootloader

@pparent Your app is very good and the improvement was made by volla 22 itself: I am now on dev 486 and scrolling on volla has improved considerably.

I struggled with this on UT. Eventually I installed dufs webdav server and I've been using that with morph. I can download files from the PC easily and I can push files to the PC easily as well using a web browser. I can even stream videos from the PC this way! [image: 1761851499424-screenshot20251030_220015506.png] [image: 1761851499669-screenshot20251030_220147457-resized.png]

@Mario.CH said in Potentially turning a negative of Google's tightening restrictions into a positave: Is that how it is in your country? Not even a post office bank? Yes, it's true that some of our banks do not have physical locations at all anymore.

@aarontheissueguy You should definitely see this post, I really think signal-desktop is the way to go: https://forums.ubports.com/topic/11532/signal-ut-signal-desktop-for-ubuntu-touch

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

@theprivacydad You're right. But also, the name is confusing. Some may think "daily channel" is for "daily device"...