@lduboeuf Thanks a lot for the suggestions. That's interesting to hear that the nuntium restart command should be the same as rebooting. It happened often enough that I feel confident saying a reboot didn't happen.
Now that I've heard your idea about booting I wonder if the trigger that would cause the issue was reboots all along. I'd be disappointed with myself for not making that connection, but it's definitely possible.

I don't have this issue anymore, it occurred both on a previous phone (Oneplus 5T) and with a different cell provider (not sure which change fixed it), but I'll try swapping my SIM into that broken old phone and see if I can reproduce it just to see.

As ever, thanks so much for your work on MMS and for the help!

@vverve Merci! I appreciate the report.

It still leaves me uncertain about what this means. When I have a call going on, the status bar always changes to 3G. Are you sure this doesn't happen?

I thought I'd seen a separate icon in a screenshot on the forum that said VoLTE on the top status bar, but maybe that changed.
It would be a big deal if VoLTE was working on Oneplus Nord N10!

@Amarurtuuq
The terminal command shouldn't have any risk, it just restarts a process. It was suggested elsewhere on the forum and I used it extensively when my phone used to stop sending/receiving MMS for reasons I could never figure out.

I wouldn't get too scared off by playing with the APN either, that can make all the difference, and doesn't take too long. Take screenshots of your current settings first, and you can always go back to that. It's easy enough to look up APN settings online for a given cellular carrier.
Some people have better luck with one APN setting for "Internet and MMS", others need to have a separate setting, one for MMS, one for Internet. It may vary by carrier or other things that I don't understand.

Even re-installing isn't a scary experience. You download the Ubuntu Touch installer, plug your phone into the computer, and then you can install without wiping data. As long as you don't unplug your phone during the process and don't wipe data, it's pretty easy.

@Amarurtuuq I'd recommend turning Wifi off altogether. I'm one of the few that has had MMS working with Wifi on in the past, but it often doesn't work.
Another thing to try is the following Terminal command:
systemctl --user restart nuntium.service

In the past my MMS used to stop working without notice and I wouldn't see incoming MMS or even an error, they were just lost to the abyss. This always fixed it, where reboots would not.

@vverve Just for clarification, do you have a VoLTE icon on the status bar during phone calls? I hadn't yet heard anything about VoLTE working on any Oneplus devices. Canada still has 3G, so it could be switching to that. When I make/receive a call my status bar switches to 3G

@FixOne That would be amazing if it were doable as a click. In any case, thanks for sharing your work on this. I hope that was an especially delicious beer.

@Linuxlite76 I've always heard of the Pixel 3a port being quite good. I doubt this is something that an update would fix, as it sounds like non-standard behaviour.
I wonder if it could be a hardware issue. Have you tried other headphones? Cleaning out the jack?
I've replaced headphone jacks on other phones and found the repair to not be too difficult, but I'm sure it depends on the phone.

@wolfgang1 If you're getting by fine for now, could make sense to wait and see how the dust settles on VoLTE rollout. And if McGill gives you any free time, you'll find folks on the Forum trying to make it work in Pixel 3a and you could be part of it. But yes, there's already great success with VoLTE on some devices.
Anyway, glad you found UT, and I hope you have a lot of fun in Montréal! I love that city.

@peat_psuwit Makes sense. I'm sure if daily is gone from installer and things are laid out in order from Stable to RC to Daily, that's clear enough.
Amazing news about MMS on Noble! Sincere thanks to those who sorted it out!

@wolfgang1 Welcome! Glad it's suiting your needs! Just note that the Pixel 3a doesn't have VoLTE working (some people are trying, but it seems tough), so it (mostly) won't work for phone calls if you're back in the USA, where 3G is shut down. Some areas might have 2G.
3G will sunset here too. Rogers, already, Telus (+Koodo, Public Mobile) Dec 2025, Bell (+Virgin, Lucky) Dec, 2026. Not sure about Videotron/Freedom.

I just checked the installer to see what was default, and yeah, first one listed in the Installer is 24.04-1.x/daily. Somebody has filed an issue on the installer's gitlab, as per another thread.

@Futura if the updater isn't giving you the option, I did see that there's a 24.04-1.x/rc, which is Release Candidate. You could flash the system to that with the installer, and just make sure the option that says Wipe Data (or something like that) isn't checked.

For 20.04, the installer has /stable, /rc, and /devel. I hadn't considered this potential for confusion before, but I guess "daily driver" is an awfully common term, and I can imagine new users being confused. Either going back to calling it "devel" or changing it to "nightly" might avoid the confusion.

Welcome!
If you're interested in using Ubuntu Touch, I'd say the best bet is to read around the forums a bunch to see if Ubuntu Touch will fit your needs, and if so which device from the Devices list will suit your needs and try to find one that's available and affordable where you are.

@theprivacydad Bad news is that uFirefox (and I think also uWolf?) doesn't have copy/paste integrated with the rest of the system yet
It's a solid work in progress, but not fully featured. The lack of up-to-date browser is just gonna make things clunky til its remedied.

And y'know, my "true Linux OS" comment is super unclear. I have no idea what makes something a true Linux OS.
With notes that I'm faaar from being among the more knowledgeable around here.. aside from Pinephones and maybe some other devices of which I'm not aware, most UT ports use Halium, an abstraction layer that's able to talk to the Android firmware involved in the components of the device. My understanding is that Postmarket OS, when used on an Android phone, is in a similar boat and uses libhybris to talk to hardware.
I'm sure it's not perfect, but I struggle to imagine a serious privacy/security risk given the sandboxed nature of UT.
As for vulnerability of the project though, I take your point, and it's a good one. I hadn't thought of that while running my mouth about the vulnerabilities of AOSP based projects
Does Halium make use of code that is at present open-sourced by Google, but could become not so at Google's whims? I don't know. But I bet somebody does..

@theprivacydad Hi!
First, it is strongly recommended not to install apps via apt. More technical users could explain this better, but my understanding is that it's because of the immutable root file system. Installing via the Open Store, Libertine, or Snaps are the recommended ways.

Not sure why the keyboard pops up when long-clicking to paste, but maybe cause some people are used to using copy/paste from the swipe-up menu at the bottom of the keyboard? I do love that menu for text selection.

Browsers are of course one of the main pain points right now. Morph is slated to get a major update to Qt6, but this may not happen for some months.
In addition to uWolf, there's also uFirefox, which isn't in the Openstore, but can be installed via a click package. This seems to be the most recent: https://gitlab.com/debclick/uFirefox/-/jobs/11063789436/artifacts/file/build/aarch64-linux-gnu/app/firefox.fuseteam_142_arm64.click
Download the .click file, and open with Openstore.
Not being IN the Openstore means it's not reviewed by the Openstore.. all I can say is that my impression is Fuseteam has been around UBports a long time and seems to be a trusted member of the community.
Not sure if one can make webapps from non-Morph browsers or not.

The full system access warning that you see for uWolf in the Openstore is by comparison to most apps being confined - sandboxed by default. This is a major feature of Ubuntu Touch, almost all apps are, and need permissions to access things from other apps, via ContentHub. Privacy-wise, it's a huge asset. I'm sure it makes things like KeePass harder to implement though.

My two cents, as a non-technical user who's been using UT as his sole phone since 2020, is that the longer you use it the easier it gets. There's definitely a learning curve, and sometimes it's just a question of finding other ways to do a thing that doesn't work the way you'd hoped. Some things are lacking and imperfect, but I've always found it incredible not just that there was a true Linux OS for phones that's so usable, but that it's so pleasant to use.
To my mind, as data collection grows and grows, (and as authoritarianism rises worldwide) the need for smartphone alternatives starts to seem kinda dire. AOSP-based ROMs are good until Google decides not to share anymore, which it kinda sounds like they're already starting to do.

Thanks for checking out and writing about UT! Whatever your review, good to get the word out.
Hope it winds up being a good, useable OS for you!

@coderyder Re: your all-caps, the README file for this port does specify that this port works on the EU and Global variants of this phone, and lists carrier-specific variants from the USA as unsupported. Perhaps this could be listed more prominently, on the Devices webpage. But to me it's unclear which American devices work or don't, and how it differs. This was the first I'd heard that the MSM tool wouldn't install firmware from other variants.

AFAIK the USA is the only place with carrier-specific N100 models. Given it's a community project, maybe more users from the USA could sort this out and provide feedback as to how it should be communicated. I don't think we can expect an unpaid porter to get ahold of all the American variants of a phone to test them all.

Hope you're able to get it working!

@Vlad-Nirky Ah, ok! I didn't know this about switching on a these things. Appreciate the tip!

@peat_psuwit said in Ubuntu Touch 24.04-1.0 Beta 1 is now available for testing:

Luckily MMS has now been looked at and should be fixed in the next Beta.

Thanks for the update - this is amazing news for those of us who rely on it! Sincere thanks to those who pulled this off!

@Vlad-Nirky Ok, this is good to know, thank you. This isn't the latest available Android 10 ROM, and it sounds like it still works fine for you.
I was probably getting too far into the details with the qjzEUxm vs qjzMIxm letters in ROMs.

I see that, within Global models, there are many different regional ROMs. Is it best to stick with the region that was originally on the phone (in my case EEA), or to use the ROM for the zone that one actually lives in (in my case, Global).
I see that @stanwood used Global (non EEA) in the instructions, but then I guess Switzerland isn't EEA, is it?

Or am I splitting hairs here and overthinking it?

@scottbouch the gitlab page for miatoll (Redmi Note 9 Pro, Note 9S, etc) doesn't list it as an issue.
But it might not be an issue for you on Poco X3 anyway. If you use Waydroid, people have a way to use the camera there without the issue. And the photos work with UT camera app, colour can just be off. There are sample photos in the Issue on the Poco X3 Gitlab page and linked from this forum post.