Hi MrRoughwood, Congratulations! And it's a very good decision to start with “stable.” Greetings Mario

@Grisen did you check the box to wipe the data partition in the installer?

Thank you @Keneda !!

@ MrT10001 I’ll wear that badge proudly. @ johndoe Thanks for the advice. I’ll keep it in mind and won’t change anything. @ liam Sorry to hear that. I’m really not an expert. So I can’t understand the issue you experienced with the battery and Postmarket on your device. Perhaps you should try again some time with UT? (Possibly a real expert should say something to that suggestion) With me the installer showed some flaws. I was absolutely not sure about how successful the install would be since it didn’t show anything like “Congratulations! Ubuntu Touch is now installed.” The final screen just showed that formatting was still at work. I could only see on the mobile itself that it was possible to start UT (since there was a reboot and I was asked to define a passkey) and that the amount of free space on the device was big enough to believe that everything was more or less OK. Hope you can still use your device somehow.

@ikoz I think i have found the solution. After allowing outgoing traffic to 188.166.175.79 port 5001 the notifications seem to work. lsof, netstat and a little bit more googling helped me. After disabling ufw; lsof and netstat were showing the IP and port after a notification came in. Port 443 is needed, too. Unfortunately logging with ufw does not work, but who cares, i didn't need it. Thanks for pushing me into the right direction, this warning app could save a life.

Most accounts nowadays force users to use app passwords when using 3rd party apps. Most likely this is what you need.

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

@rubencarneiro Can you give infos about that ? You were some time ago involved in doing logos for devices, how can it be done now, someone should fill an issue on device git ?

@RJDan You can wait for the esim manager in UT although not sure when it'll land. You can probably try it out from the repo. Or you can reflash Android, set up the esim there then reinstall UT.

@artur_ it dons't work, show error: FAILED (remote: 'Failed to write partition table') how to fix it ? [image: 1752159572465-6b8f3a24-0adf-4272-bf8d-2a003c7ec007-image.png]

@Alternatif did you solved the issue? I am suffering the same issue, can you share the solution? thanks

@fair OSK will be disabled by default when an external keyboard is detectedm You can only force enable the OSK in this case but you can't force disable it.

Addendum 2: Of course, it could be BT, but I thought I'd check-in with you guys first before tackling the behemoth; but to be fair once you get to a actual person, I have found they were knowledgeable and helpful. Anyway, as the problem hasn't been reported here, I'll adduce it's some glitch involving BT and close this question; and my life can move on. Thanks for the (tacit) help.

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