@kugiigi Hello, Thank you for the inspiration to help others. Below are instructions for installing a single ProtoVPN Wireguard and multiple ProtonVPN Wireguard configurations along with method for mitigating autoconnect conflicts between them. INSTRUCTIONS TO INSTALL PROTON VPN WIREGUARD ON UBUNTU TOUCH 24.04 DOWNLOAD WIREGUARD CONFIG FILES FROM PROTON VPN WEBSITE https://account.protonvpn.com/downloads Give simple name (i.e. wg0, wg5, wg9, etc) to config file Select platform: GNU/Linux Select VPN options: (Block malware, ads & trackers) Select: VPN Accelerator Select either "Standard" or "Secure Core" configs Scroll down to choose and select "Create" Download conf file and make copy with simple name (i.e wg0.conf) WIREGUARD CONFIG INSTALL ON UBUNTU TOUCH 24.04 Manually Toggle WiFi OFF Open Terminal where wg0.conf file is located Execute following terminal commands: A. nmcli connection import type wireguard file wg0.conf B. nmcli connection modify wg0 ipv4.dns "" ipv4.dns-search "" ipv4.dns-priority "" C. nmcli connection modify wg0 ipv4.dns-priority -50 D. nmcli connection down wg0 && nmcli connection up wg0 Manually Toggle WiFi ON Check IP Address: https://protonvpn.com/what-is-my-ip-address MULTIPLE WIREGUARD CONFIG INSTALLS ON UBUNTU TOUCH 24.04 Manually Toggle WiFi OFF Open Terminal where wg0.conf file is located Execute following terminal commands: A1. nmcli connection import type wireguard file /path/to/wg0.conf A2. nmcli connection down wg0 B1. nmcli connection import type wireguard file /path/to/wg1.conf B2. nmcli connection down wg1 C1. ... C2. nmcli connection down wg# D1. nmcli connection import type wireguard file /path/to/wg9.conf D2. nmcli connection down wg9 To prevent conflicts with wg0 and all other wg# connections: A. nmcli connection modify wg0 autoconnect yes B. nmcli connection modify wg1 autoconnect no C. nmcli connection modify wg2 autoconnect no D. ... no E. nmcli connection modify wg9 autoconnect no nmcli connection down wg0 && nmcli connection up wg0 Manually Toggle WiFi ON TROUBLE-SHOOTING VIA TERMINAL To check wg0 connectino status: A. nmcli device status To delete wg0 and start over: A. nmcli connection delete wg0 To start wg0 connection A. nmcli connection up wg0 To stop wg0 connection A. nmcli connection down wg0

@nogoogle Bad news... Maybe you'll have to return to Android and test to be sure the hardware has no issue.

@nogoogle I don't know why I didn't think of this before, but the whole reason that I left Telus was because they said that due to network changes, my device (then a Oneplus 5t) would no longer have functional MMS. https://www.telus.com/en/support/article/picture-and-group-messaging-changes The linked article says "older decices", but other communication from Public Mobile said the only way to be sure was to use a phone from a fairly small approved list, which FP4 isn't on. Maybe some kind friend who uses another network would let you briefly borrow their SIM for MMS testing, to see if changing networks would solve it.

@wynn1212 Thank you for your detailed reply. I was using Ubuntu 24.04.2 with Kernel Linux 6.8.0-57-generic both on and old AMD desktop first then on a Windows Surface Laptop (running same Ubuntu version) with a USB2.0 to USB C cable. Next I tried a USB C to USB C cable on a Dell laptop (also running latest Ubuntu version) and after 2 or so attempts the flash was successful (not clear why). However today, I did the same procedure with another new FP4 using the Dell Laptop and USBCtoC cable and it again failed initially. When I connected the phone (already in fastboot mode) and restarted the bootloader from fastboot when installer was asking to manually switch the phone to fastboot, I was successful. This is quite frustrating because it still is not clear to me how to exactly reproduce this issue. It is definitely not the cable or the computer used. I agree this must be an interaction between the Ubuntu version and/or kernel and the phone. It almost looks like a timing issue, restarting bootloader at the right time lets the process go through. I could not test on Windows because I only have a work laptop running windows which does not allow starting non-certified appimages.

@nogoogle There is an odd issue with the PP not sure of PPP where if the device has a sim pin when you set up the phone it causes issues. If the sim has no pin all works fine. I found this out by trying each way. You might find out more by going to the Pine 64 group on Telegram https://t.me/utonpine Another similat issue is that the APN settings "green" switch does not stay on either,

@nogoogle That is weird... Good luck with that

I'll try to answer base on what I know. Note I might be wrong though Just check the update page and make sure to install all app updates. If it shows no update then you're most likely in the latest version. If you're on stable channel, I believe push notification is enabled so you'll get one if there's a new update. If you mean the link below, then no they're unrelated. That's just a job that builds the same image (or stable) over and over again and it was daily before so the number got really big. Just ignore these builds. You'll only need it if you want to reflash. https://ci.ubports.com/job/rootfs/job/rootfs-pinephone-systemimage/ No I'm not in stable channel on my pinephone right now so I can't see it myself and refer but in the OS build details page, you'll see different values such as UBports Image part and Device image part. OS Build number shows your current build number. Not sure if the pinephone shows "OTA" label or just build number for now. UBports image part is the build number/date for the rootfs or the actual OS. Device image part is the build number/date of the device specific software such as kernel. I'm not completely sure on this but this is what I know