Thanks to recent developments, SMS and MMS fixes for users of various Halium 9 ports such as the Pixel 3a (XL), OnePlus 6, and others make it possible to get reliable SMS and MMS (only with wifi disabled right now) working for North American carriers, which previously had not been consistent.

• Note: Even with these fixes, MMS incoming group messages aren't delivered to the Messages App correctly. MMS Photos work fine in and out, and sending MMS group messages work. Here is a brief guide to getting this working:

SMS

• IMS services need to be disabled as part of the port, since if those services are running then carriers may detect your phone supports IMS and convert the way they deliver SMS to your device causing all your SMS to go down a black hole!
  • Pixel 3a: please move to the "RC" or "Devel" channels, which have the patches already applied to disable IMS services.
  • Other devices: if you receive 1 SMS after boot then no others, it likely is IMS interference. You may need to contact the porter of your device to discuss with them disabling IMS services.

MMS

• Step 1: Apply MMS patches

  • Note: for the Pixel 3a using "RC" or "Devel" channels, only the first patch for "nuntium 8" will actually make any changes.

• Step 2: Install updated ofono and ofono-scripts packages.

  • Somehow get a terminal running on your device: recommended is enabling developer mode in System Settings > About then using adb shell when connected to a computer via USB-C. Otherwise, you could connect via ssh [if you have that set up](link url).

  • Run these commands:

    • sudo mount -o remount,rw /

    • wget https://ci.ubports.com/job/ubports/job/ofono/job/xenial_-_android9_-_usissue/lastSuccessfulBuild/artifact/ofono-scripts_1.21+ubports1+0~20210819100145.2~1.gbpb9f999_all.deb

    • wget https://ci.ubports.com/job/ubports/job/ofono/job/xenial_-_android9_-_usissue/lastSuccessfulBuild/artifact/ofono_1.21+ubports1+0~20210819100145.2~1.gbpb9f999_arm64.deb

    • sudo apt install --reinstall ./ofono*.deb

• Step 3: Reboot

Again, at this time, MMS send and receive only work with wifi disabled. If you have issues with your APN Settings then try to Reset ALL APN Settigns, reboot, and re-enter them based on your carrier specifications. Note that another bug prevents setting Internet and MMS as the APN type: use MMS only, but do NOT create a duplicate APN for Internet in this case: 2 APN entries with the same APN will cause MMS to not work! So effectively, in this case, just set up the APN for MMS only and Internet should also work.

Join the UBPorts [North America Carrier Issues] if you need interactive support in getting SMS / MMS working.

Is there any consideration in having a separate build that is not a read-only filesystem, e.g. more of a standard Ubuntu install? If there were something like that, I would think it could stand as the main development branch that would allow faster upgrade to 20.04 / wayland / systemd / etc. Then it could be a testing ground that new releases of the "stable" or "consumer" read-only system would come from.

It would also not frustrate any potential developers who want "standard Linux on a phone" (mobian, manjaro, fedora, etc.).

In summary, I understand a lot of the reasons behind the read-only system for stability, for security, for end users, etc. but I fear it keeps away possible developer interest that would benefit Ubuntu Touch in the long run if it were more "traditional Ubuntu" on a phone?

People could be trying all sorts of things like flatpak / snap / different apps, etc. I know there is Libertine but there is some performance issues and it isn't available everywhere, etc. So take the chains off and see what happens? I suspect a large growth of the community (???)

@ubportsnews there have been different comments here and there on some possible contract work for enabling VoLTE being undertaken by someone outside the core development team. Can you comment on or link to this work so we could have a better understanding of it?

Since it seems a solution may need to be a combination of software + firmware support will it be a case-by-case basis to have devices support VoLTE or will it be able to be enabled for all Halium 9+ devices for example?

@joshndroid thanks for starting the thread.

All developers and contributors, thank you for everything you have done to bring us to where we are today with Ubuntu Touch.

Updated Nov 6, 2023

Last year when T-Mobile shut down their 3G servers (and said they were going to shut down their 2G servers as well) we thought it was the end of the road until UT would support 4G calls (VoLTE). In fact many have left UT as their daily drivers because of the lack of telephony functionality since that time.

However, the T-Mobile 2G servers are still functioning until April 2024, so they can be used for calls as a stopgap. Note that time is running out, hopefully UT will support VoLTE calls before 2G is shut down!

Also note that in 4G mode cellular data works fine, but calls do not auto-negotiate down from 4G to 2G and so incoming calls will be missed. Previously when the 3G network was still up, UT would auto-negotiate down from 4G to 3G when a call was coming in, meaning the phone could be kept in 4G mode. But with 3G servers offline and no auto-negotiating down from 4G to 2G for calls it means leaving the phone in 2G only mode is the only way to reliably receive and make calls. Data speeds are slow, but that saves your MB! So use 4G mode for speed (but no calls) or 2G mode for calls and slow speed

Until relatively recently, we used to have to set multiple APN entries (one for cellular data, a second one for MMS), and this was confusing because many providers only have a single APN, so we had to use a mixture of APNs from multiple carriers to get around the problem. Thankfully, we can now correctly use the Internet + MMS APN type in UT, so it is much more simple to set an APN correctly.

Below are some collected APNs for T-Mobile and T-Mobile MVNO carriers in the USA:

T-Mobile USA APN Settings

Used For: Internet + MMS
Name: T-Mobile
APN: fast.tmobile.com <NOTE: do not use t-mobile.com it will not work!>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
<Proxy, Proxy Port, User Name, Password ALL BLANK>

Alternative:
Used For: Internet + MMS
Name: T-Mobile
APN: epc.tmobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
<Proxy, Proxy Port, User Name, Password ALL BLANK>

US Mobile APN Settings

Used For: Internet + MMS
Name: US Mobile
APN: pwg
MMSC: http://pwg.mmsmvno.com/mms/wapenc
<Proxy, Proxy Port, User Name, Password ALL BLANK>

Mint Mobile APN Settings

Used For: Internet + MMS
Name: Mint Mobile
APN: wholesale
MMSC: http://wholesale.mmsmvno.com/mms/wapenc
<Proxy, Proxy Port, User Name, Password ALL BLANK>

Tello APN Settings

Used For: Internet + MMS
Name: Tello
APN: wholesale
MMSC: http://wholesale.mmsmvno.com/mms/wapenc
<Proxy, Proxy Port, User Name, Password ALL BLANK>

To make sure the settings are applied, after changing APN entries please reboot.

Note that, yes, it is known that 2G audio isn't great for calls, but hey it is a functioning phone!

Please reply here with other MVNOs that may work in the USA, I will keep updating this post to stay current.

Thanks again to everyone for the hard work. I am a big supporter of this work, but am a bit lost: the recent work seems to be focused around multi-window, etc. for desktop, which I would think is 2nd level priority over getting apps to work well "full screen" for phones. Is it all needing to be done at the same time, or can enough polish be made for phone users first, then those testers and feedback can inform desktop work as a 2nd stage? Maybe phone use is already polished enough, but I have thought it isn't ready to test yet?

@UniSuperBox

"Don't worry, your grandfather died doing this work!"

That was a strange way I was greeted one even in Khartoum, Sudan, in 2010 as it was well past sunset and I was still working away on the network infrastructure at the NGO I was volunteering with. The speaker was this elderly Sudanese man who was encouraging me that I couldn't get it all done in one night, so take some rest. His words sounded funny though because my first thought was: "Huh? My grandfather didn't know anything about running CAT5!?!" but as I thought about it what he was saying was "you can't do it all, there will always be more to do than 1 person can do." In some ways that is "fatalistic thinking": will we never make it?? But it is also true.

So this is what I am acknowledging and passing on to you to, good sir:

"Don't worry, your grandfather died trying to get 20.04 out the door."

So, wishing you a good break and a re-kindling of passion. We will make it with help from the community that ebbs and flows but continues on.... it may not be as you thought it would be when you first took on the reigns as Development Manager, but you have led us a long way, and you deserve some rest and acknowledgement that your effort was so appreciated by so many.

@linux-is-life great to hear it is working well. What carrier do you currently have again?

Can you confirm incoming SMS work reliably (more than 1 in a row) when on 4G (even though you prefer 3G)? We had a big problem with that on Pixel 3a and I am curious if it is a problem for other phones or not. If it is, there is a way to fix it.

Also, can you comment on MMS photos: can you send and receive? (you may need to be OFF wifi for it to work). So please report on that and if you need to disable wifi or not.

Also, to reply to your question about carriers, in the USA I use US Mobile, with the unlimited text + calls + 1GB LTE data for $12/month ($16.48 with tax and fees for me). They are very easy to use and have a responsive customer service. For Ubuntu Touch use the "white GSM" sim they give you (T-Mobile) instead of the black one (Verizon).

@UBportsNews I have understood from previous Q&A sessions that some of the major development goals include:

• moving to systemd
• moving to 20.04 base
• moving to wayland

Any updates on these goals and how they inter-relate? systemd for example we heard briefly from Marius went better than expected when working on Lomiri for Manjaro Arm.

Erfan posted this reply to my above question on telegram:

"Hey i was just going to reply your post in forums that noticed you are already in group so if u don't mind i'll answer here

first of all thank you very much for your support, really appriciated
but recently focus was in finalizing application managment in display instead of a full android screen
for weekly report i just said said multi-windowing but in reality the work behind of it was more for detecting/selecting open apps in screen

now i'm working on a sever-like tool to glow this pieces together and have something usable for users with proper app managment"

gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties

Is this the most definitive way to tell if the phone is VoLTE capable or not?

We did get confirmation from @Inali that with this command their device does show "VoiceCapable": <true> so I think it is a good command to confirm if the phone is IMS registered and active. They did have issues making or receiving calls as it was starting a double call (one in 2G, one maybe with VoLTE we think?) and also SMS is broken with VoLTE enabled, but this also showed in the command. So a few steps forward at least!

@mariogrip we are collaborating on the North America Carrier Issues telegram group, and are not certain how to determine if a call we make is indeed with VoLTE or instead 2G. @tigerpro and @Inali are there and set for testing, as am I.

If we use the list-contexts ofono script and it shows the IMS context is not active, does that mean it is not able to do VoLTE yet? Or instead, @fredldotme gave us this command to check:

gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties

Is this the most definitive way to tell if the phone is VoLTE capable or not?

If you could give your input on what is the best way to know if we have done all the magic to have the device capable of VoLTE it would help us know what we are dealing with. Thank you for everything along the way!

@lduboeuf said in Can't receive SMS:

No issue for me since a week now on 20.04 ( devel updated each day, and device shut
down every evening )

Great news! To help understand, can you help me remember what piece(s) seem to have fixed the issue for you? Was it the updated ofono, the updated nuntium, or other? Since there were multiple things going on I am not sure where the SMS reliability issue was addressed. Any link to the key issue would be appreciated.

@wizardi3 of course it is not certain, but in our discussions on the "North America Carrier Issues" telegram group, our speculation is that there isn't a lot of motivation for T-Mobile to shut down the 2G network. It's frequency spectrum doesn't conflict with pending 5G (that is why we understand US carriers have discontinued 3G: to free up the frequency band for 5G). Also, there are existing 2G industrial and commercial customers (warehouses, package tracking, etc.) that they make money from.

So, it certainly can be the case that they will shut down the 2G band with little warning, but we are hopeful that it will last long enough. In the meantime it remains the only way to have a working UT phone in the USA, so we will stay with it until we can't

@wizardi3 said in USA: T-Mobile (and MVNO) 2G settings for a fully functional UT device:

T-Mobile is phasing out 2G this month.

Do you have a source for this? According to their own site (link in first post above), "We’ve also shared that we plan to retire T-Mobile’s older GSM 2G network as well, but no date has been set. We will update this page with any additional information in the future."

@lakotaubp and @mw4jet I have joined you with a P3aXL 20.04 install on a secondary device. A few observations:

• Calls work in 2G mode (T-Mobile mvno) the same as in 16.04, but no MMS (MMS is working in 16.04).
• Mobile data doesn't seem to work in 4G or 2G modes (this is likely why MMS doesn't work if no mobile data then no MMS?).
• Disabling wifi doesn't seem to work (it re-connects / re-activates).
• Bluetooth doesn't seem to work.
• The open store is basically empty

So for any of the above bugs (mobile data / bluetooth / wifi re-connecting) should I report them or just hold onto them for now?

@ultrasonicnoise what country are you in and what carrier are you using?

@mdl I am sorry to disappoint you, but from our testing your ONLY option for UT to work with USA carriers is the above T-Mobile (or mvno) settings. ATT, Verizon, and T-Mobile all dropped their 3G networks last year and I don't think (??) anyone has gotten ATT or Verizon to work in 2G mode. 4G (LTE), as noted above, is not yet supported by UT Until very recently, we all thought there was NO carrier working with UT after the drop of 3G networks. Thankfully T-Mobile still works in 2G, so that is as successful as we are right now!

@mw4jet said in USA: T-Mobile (and MVNO) 2G settings for a fully functional UT device:

@rik I saw your posts on Telegram and figured I would give this a try. I had just reflashed my OP6T back to android 12 to peddle on Ebay, so I reflashed to UT and find no change from what I had before, Calls in and out, SMS in and out, no MMS at all. I have it in 2G on US Mobile.

Sorry I have lost track of your specific issues, but MMS photos should be working on US Mobile (T-Mobile). You do have wifi disabled when attempting to download a MMS, correct? Additionally, if it is a group MMS then you need the group pre-created (this is "fiddly": you need to look in the error log to find what phone numbers are part of the group message, then manually create the group with those numbers, then again attempt to download). I think @rocket2nfinity has an OP6T and can confirm that MMS is working in 2G mode.

Do you have any other MODS on the device? I had done some fiddling to the phone before but it's all stock UT now. I have a Pixel 3A but I cannot try it on US Mobile as it was supposed to be unlocked but it only works on AT&T so I cannot try that one.

Sorry you got a carrier locked one. For me, yes I did some "fiddling" in the past, but am now at "stock RC channel".

@keneda said in Is there a phone that actually calls (USA networks) with UT?:

@rik
So that means under UT it is VoLTE capable also in EU, and in the rest of the world ?

That kind of "detail" is important to better spread to UT users.

For instance, at least, it should be mentionned in its device list page under "cellular" https://devices.ubuntu-touch.io/device/cheeseburger/

Well I think it is more of a "huh no one knows why it works" situation: again UT can't make a call out in 4G / VoLTE even though incoming calls do get received. I think it is sort of in the "we won't really announce this as a feature because it is half workable and really needs looking at". But I don't own a OP5 so I will defer to what others think.