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

@scottbouch I think all devices still say that VoLTE is unsupported. This was explained somewhere as being because it's still in beta, and the website will be updated when VoLTE is more fully rolled out.

Can't speak to UK, but having recently needed a new phone, and with 3G sunset looming in Canada, I was in a similar position. The Poco X3 NFC sounds like a great port. One small issue with the camera taking slightly off-coloured photos (on device's gitlab there are photo examples). But it sounds very well supported, and people report good success with VoLTE.
I wound up buying a Redmi Note 9 Pro, as there was a cheaper deal for a new in box one (the Lithuanian seller I bought from on eBay still had two others recently).
Beyond Fairphone and Volla, these are the two phones that I know of where VoLTE seems to be working (as well as other Miatoll devices similar to Redmi Note 9 Pro).
But of course officially VoLTE is in beta. If one could wait longer, maybe the landscape would become more clear. Not always an option to wait though, I know.
Sounds like you'd be wise to check into network compatibility with each phone too.

Hopefully a UK user can offer an experience.

@Futura Are you on Noble, 24.04? MMS is a known issue there.

If you're not, well, I don't mean to say that MMS always works out of the box
Sometimes it does, sometimes it can take some fiddling. But it does work for a lot of people. I couldn't daily drive UT without it.
First thing to try in my experiences is playing with two separate APNs, one for Internet, one for MMS, vs one for combined Internet and MMS.

@arubislander Ok, I see. It's not a world I know much about, and I appreciate the clarifications!

@arubislander Ah, ok. Thanks a lot for the explanation.
So if I understand right, with Snaps now enabled, we have access to desktop apps through a different avenue than before (maybe more easy to work with than Libertine?), but the only apps we're likely to see there that are mobile friendly out of the box are those already being made specifically for UT?
Flatpak is used by other mobile linux distros, thus should have more mobile-friendly apps, but even if we made flatpaks work in general, the apps within pose challenges because they're made using GTK and Ubuntu Touch uses Qt?

@Futura Thanks for the thoughts, and the tact with which you handle UT's shortcomings for your situation.

I'm surprised by your SMS experience. I've never heard of this delay before. I use SMS and MMS and it's more or less instantaneous.
It may be the case that on some devices, VoLTE is causing issues with SMS/MMS? And I heard that it's not working yet in 24.04. But both VoLTE and 24.04 that are in beta, and are being worked on.

As a fellow North American, I share your desire for RCS. It's not that I'm in love with the format - personally I hope the EU succeeds in making messenger apps interoperable the way email is. The problem is that that people here send RCS/MMS with the absolute expectation that it will be received, because it's free with every plan. Major problem here when it doesn't work.
My impression is that few if any of the core developers of UT are North American, and in most places in the world, RCS/MMS is hardly used, and definitely not taken as a given for anybody with a smartphone the way that it is here.
This said, group messages aside, MMS works pretty well for most people! Photos between myself and those using iOS and Android phones default to MMS and go through fine. I've always had the odd quirk, and sometimes would miss messages without seeing any notification, but I found a carrier where I always do at least get a message that an MMS couldn't be downloaded.
Unfortunately there aren't any easy answers to get RCS. UBports is driven by volunteers, devs are expensive, and the work is time consuming. There have been a tonne of big things to solve lately, and that are being solved / have been solved! From a global perspective many things are just bigger priorities than RCS.
Often we North Americans can tend to think that the world revolves around us, and it really, really doesn't. In a UT context, we need to learn to fix our problems ourselves and not expect volunteers to want to solve problems that don't apply to them or those around them when there are bigger fish to fry.
So I guess you and I can learn to be wizards at coding, find local devs willing to take this on, or raise a large enough bounty to make it worth somebody's time. Bounties seem not to be impossible, but I think it takes a lot to make it truly worthwhile.
Meanwhile, you could play with APN settings, borrow a SIM or take a cheap plan to try different carriers, and see if you can get SMS and MMS working normally, and support the UT project in any way you can.

Flatpaks sounds great, but again, it takes somebody doing it.
Without any interest in wading into a Flatpak vs Snaps debate, I'll mention that we do already have Snaps. To my mind, effort might be better spent getting more apps from Snaps working in a UT setting. Most Linux apps aren't exactly made for mobile, and whether we have Flatpak or Snaps, it's not going to mean that everything just works.
Meanwhile, some of us get by ok without using Waydroid at all, and with more up to date browser coming along, it'll get even easier to use more websites rather than apps.

One thing that us non-devs CAN do is communicate about the current state of affairs. I've always liked the Forum for this - easily searched and read by anyone. I feel that the website Devices page does a fairly good job too, and the Q&As are great!
But we can all brainstorm the best way to communicate things, pitch our ideas, and make it happen. https://ubports.com/community-center

Hope you're already able to solve the issues you're having and are able to use UT successfully and happily!

@Simmonz Can be worth playing around a bit with APN settings for MMS. I needed two separate APNs for Internet and MMS. I was able to use a tethering APN for my Internet and the nornal one fot MMS. Some seem to need this, others have found the opposite, that it only works with combined Internet and MMS on oneAPN setting.
I still lose about 1 in 10 of incoming MMS messages, but at least I get a notification.

If you're able to test VoLTE, I'd be very interested. I believe it should have a VoLTE icon in your indicator bar at top when connected on a call if it's working properly. Insights on call quality, and whether SMS works normally with VoLTE enabled also welcome.

Too bad about reception. Not sure why it would be worse with same device on UT vs Volla OS.
Thanks for the info!