Merry Christmas and Happy New Year to everyone!
In my country I can check "Snow", as there's a snow layer about 25 cm (10 inches) on the outside here, that did not happened at Christmas for >10 years.... 
I'm already looking forward to a year 2025 full of exciting challenges for Ubuntu Touch! And above all: A huge thank you to all those who keep this magnificent operating system so Great.
Well, OnePlus Nord N100 is not a "2G phone" and should connect at least on 4G frequencies (5G is coming soon on Ubuntu Touch, may already works on a few devices...?)
The problem is that Ubuntu Touch does not yet support VoLTE (calls on 4G), and that is mandatory on almost all carriers is USA now. Maybe, only T-Mobile does still support CSD standard phone calls?
VoLTE and IMS services are pretty hard to implement due to their proprietary features, lack of documentation and carriers white lists.
However, a deep work is in progress from our core team and it will slowly be available on more and more models during the next months.
There's a dedicated Telegram Group where you can talk about this. Search for "UBports [North America Carrier Issues]". You will find some workarounds and other useful information. You will also be able to share ideas with other North American Ubuntu Touch users.
So this is the status of your issue right now...
Fix has been officially pushed to dev channel (Thank you Adam).
I therefore did close the issue:
@vince-vs So I guess it's device specific since I've got no issue on my Redmi Note 9S.
Perhaps something you could try is to reinstall using UBports Installer (don't check wipe nor bootstrap options).
@vince-vs I think you did duplicate your question here:
https://forums.ubports.com/topic/10627/focal-ota-7-available-today/5?_=1733418376741
@vince-vs Maybe MTP protocol isn't for some reason active anymore?
You can download "Ubuntu Touch Tweak Tool" in the OpenStore.
Open the app, Go up left on the 3 dots, select => System => ADB settings => USB mode and select MTP - Media Transfer Protocol.
Then reboot the device and see if it works.
@jojo WhatsWeb is a Web access of Whatsapp, so it needs to be paired to an official device that's use the real Whatsapp application.
Unfortunately Nexus 5 is dropped down by UBports and runs an ancient and deprecated version of Ubuntu Touch. It currently uses the old Ubuntu 16.04 repositories.
The reason is that it's somehow pretty hard to be upgraded to a newer version due to its old hardware. Currently Ubuntu Touch is based on Ubuntu 20.04 Focal, and will move to 24.04 Noble in the upcoming months.
For the same reason, it's not compatible with WayDroid container, which runs only on Halium 9 and < ports. Nexus 5 is based on Halium 5...
So I'm sorry, but there's no chance to use Android apps on Nexus 5 using Ubuntu Touch so far.
@elysian893 I guess you did install UT yourself?
To do so, if I'm right, you first have to revert back to Android 11 before installing Ubuntu Touch. The reason is that the device has been ported on Android 11 and thus it needs specifically those vendor firmware from Fairphone. If in the meantime the device has been upgraded to A12 or 13, then there are large chances that you will get issues on the general use.
@elysian893 Ok than. Did you try your SIM card in another phone, just to ensure that it's not something related to your subscription?
Did you try to change your location to try another cell tower?
A part from that, it's pretty hard for me to tell you some more as I live in Switzerland.
Just from my experience here, I use my home carrier (Salt.) and I've got 4G cellular data that work pretty well. I did not have to change anything in the phone settings. Now Ubuntu Touch is able to download the carrier's cellular settings directly from the SIM card.
All operators in Switzerland did stop MMS last year since it wasn't really used by people anymore - due to all third party messaging apps. So MMS field is now empty. Only the profile "Internet" is used.
Hope you will find decent help further...
@elysian893 Oh Sorry then. Sometimes it's needed to restart the device after having changing cellular settings.
Did you try to change the name from "Metro" to "MetroPCS" as indicated in the guide?
@elysian893 Did you try this APN instead?
Don't know if it's right, but there's a guide for manual cellular settings on MetroPCS by T-Mobile:
@elysian893 Not sure if Fairphone 4 is compatible on this carrier.
I did travel in North America in August 2023 with my FP4, and it worked well on Roger, Bell and Telus (Canada), and on T-Mobile and AT&T (USA).
Visited area: Quebec and New Hampshire (and parts on Vermont). I was mainly based in Montreal.
There's this topic, but not really related to MetroPCS:
There are also those Telegram groups for you:
UBports [North America Carrier Issues] but I'm unable to copy the link
https://t.me/ut_on_fp4 (Ubuntu Touch on Fairphone)
So not a clear solution I admit, but some clues to help...(?)
@danfro Got it! I just notice that a log file named "tedit.log" has been created in my home directory on my PC, funny isn't it?
So I could pick it up in my Thunar files manager and copy - paste the information of a sequence below. So here we go:
Dec 02 22:38:15 ubuntu-phablet systemd[2701]: Started lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service.
Dec 02 22:38:15 ubuntu-phablet aa-exec[18696]: library "eglSubDriverAndroid.so" not found
Dec 02 22:38:15 ubuntu-phablet aa-exec[18696]: Creating a QMirClientScreen now
Dec 02 22:38:19 ubuntu-phablet aa-exec[18696]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/1.3/TextInputPopover.qml:56:9: QML Action: Binding loop detected for property "enabled"
Dec 02 22:38:19 ubuntu-phablet systemd[2701]: lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service: Main process exited, code=killed, status=11/SEGV
Dec 02 22:38:19 ubuntu-phablet systemd[2701]: lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service: Failed with result 'signal'.
I can provide you more sequences if you need, although there are not so much differences.
Hope it could help.
@danfro Thank you.
I could successfully pair an ADB shell connexion between my smartphone and my PC (Xubuntu 24.04).
If I run
adb shell journalctl
I have thousands and thousands lines in return.
But if I run:
stanwood@stanwood-K53SV:~$ adb shell journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service >>tedit.log
stanwood@stanwood-K53SV:~$
then, as you can see above, I have nothing returning. Sorry I'm really noobs on technical commands and stuffs like that... should I change "user" by "phablet" or something else?
Thank you and sorry once again for my very limited technical knowledge.
@danfro So I shut the device down during the night as I used to, and started up this morning. No change.
Don't know where to find the logs (I'm not keen on installing apps such as "Log Viewer", which can lead to system instabilities).
@messayisto Same here: Deleting cache + config + data does not help.
@danfro said in tedit development and design discussion:
Could you please try the build from the latest pipeline?
Ouh... Don't know how to install this, I couldn't find the .click file in the "artifact.zip". But I acknowledge that I'm not skilled at all....
@danfro My test was the simplest one: Just open Tedit, type "test" on the field, then press and hold my index finger on the word ‘test’ that I've just written. The app closed immediately.
Now I just tried something even more simple: Open Tedit, press and hold in the empty space (nothing has been written), and the app closed (crashed) as well.
In both cases, no other app was opened nor active.
Hope that it can help...
@messayisto Same on Redmi Note 9S, but as I don't think I did try this before, I have doubts that it could be related to OTA-7... (?)