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

I know this is an old thread, but it seemed the most relevant place to report:

Today I received a cell broadcast! Emergency alert test in Ontario, Canada. Running 20.04 OTA-6 on a Oneplus 5T.
Phone was on silent, so I just heard the vibrations and saw the message.

Way to go team! Many thanks to Lionel and others who've worked on this!

Clarification for future readers of this post that might be considering Ubuntu Touch in Canada: All 3 major Canadian networks have stated that they're maintaining 3G until December 2025. Different story in the USA, where at different points in 2022, the major networks discontinued 3G.

In Canada, Ubuntu Touch is very much usable as a phone. Telephone calls, SMS, MMS photos, audio, and video all work as expected for me. (Group texts do not, and MMS has caused me plenty of headaches in general, though I think I've got a stable setup now.)

Hopefully VOLTE can work soon. I'm much too inept to be of use in that quest other than to keep donating to UBports and crossing my fingers. My enduring gratitude to those working to make UT better. It's already improved considerably since I started using it in late 2020.

Big thank yous @Moem for showing your work on this and @danfro for getting an up to date Cinny app for us all. Really, really appreciated!

A bunch of work has gone into browsers, but nothing's working perfectly for now.
For me, Morph is still doing the job for the most part. I allow it to keep tabs open from session to session, and put passwords in when I need to.
uFirefox has filled the gap for some websites that didn't work, although now there's uWolf, a fork of Librewolf, that I hear is making a lot of progress.
My understanding is that the idea is to package whatever Qt 6 components are needed with Morph in 24.04, and then we'll have a much more up to date browser. And ideally a Firefox based browser like uWolf too. There was even impressive work on a Webkit based browser, Mimi.

As for email, mine happens to work fine in Morph. I haven't used Dekko in a while. Maybe the dev has stepped back or been busy and nobody stepped up to take theIr place? I didn't realize it had so many issues, but the answer to why there isn't (x) in UT is because you and I didn't do it.
But I appreciate that you know this, and maybe others will have solutions/workarounds to specific Dekko 2 issues.

Overall, a tonne of work and resources have been going into the upgrade to 24.04 and some other major improvements, like VoLTE, and encryption. Big, big accomplishments.
After 24.04 lands/stabilizes, perhaps somebody will have time for Dekko.

Welcome back! Hope you find solutions that work for you!

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

Cool! Thanks for the demos, nice to see your progress! This is going to be very useful.
Thanks so much for all your work!

Hey @shodan,
Welcome to the community!
I wouldn't give up on the phones you got just yet. After a quick bit of searching, I can't find any such phone as a Oneplus N10 Metro. I don't know much about these things, but could the device be locked to a cell carrier called Metro, and maybe that's coming up in the installer? In searching for a Oneplus N10 Metro, I noticed there's a cell company in the USA called Metro that seems to supply Oneplus N10. Sometimes a device is locked to a carrier, but often it is possible to unlock it. May be worth searching online for how to unlock the phone from Metro? But again, I'm really not sure this is the case.

Also, I see that you have Android 11 installed. In the device page for the OP N10, if you scroll down a ways, it states that you'll need to be using a specific version, Oxygen 10.5.7 or something. The system image or whatever you call it is conveniently linked from the device page. You'll need to download that file and install that version of android before installing Ubuntu Touch.

The other main thing you'll need to do , probably before downgrading, is unlock the bootloader. Search online for how. Takes a bit of doing, but it's all doable.

General installation instructions for Ubuntu Touch are found on the installer page.

Hope it turns out that your devices are what you thought they were, and useable for UT!

@RJDan This topic is for testing 20.04 OTA 10. Sounds like you've upgraded to 24.04. There's a separate topic for 24.04.

I think apps not opening makes sense. Not all will work out of box on 24.04, and will require action by the app developer.
If you've gone to 24.04 without intending to, maybe wait for somebody more knowledgeable than me to suggest how to go back. I thiiink you should just be able to flash 20.04 Stable / RC without erasing data and that should be fine? But I'm not sure.

@atarilinux I'll start by saying that VoLTE, while being used daily by some, sounds like it should still be considered in beta across all devices.

You're right that Volla and Fairphone don't sell outside the EU, at least for now. @AppLee recently mentioned that Volla is looking into official network support in North America, so who knows, maybe they'll sell phones here one day.
Meanwhile, there is Murena, a third party vendor, that will sell Fairphones to NA, or third party shipping services, which I know little about, but will ship here for a markup.
There are also Fairphone 4 phones on eBay from a vendor called NeverMSRP that I considered for a bit. They seem to have good reviews.

But there are also people using Xiaomi phones with VoLTE, including in USA I believe. Poco X3, Redmi Note 9 Pro, and maybe others. The ports for these phones seem to be solid and supported. I found those phones hard to find domestically, but careful searches on eBay yielded international vendors who'd sell to Canada, though tariff stuff may be complicated in USA.

And then Brax3 phone and Furiphone FLX1 are both making ports of UT, though we're awaiting details. Both play well with USA networks though.

Hard time to make a decision, with VoLTE and 24.04 still in progress, but we can at least help each other be aware of the options and make the most informed decision possible.

@b15063368 Unfortunately I can't answer many of your questions, but I think that a number of games in the Open Store use Godot.
If you don't hear back from anybody here on the forum, you can always try the Telegram groups, where often developers are more active.
Thanks for your interest in making apps for UT!

@UBportsNews Really amazing news. Huge thanks to all the devs!!

@oldbutndy Yeah, as rocket2infinity says, no guarantees about VoWifi. But I thought some people had said that it "just worked" after VoLTE was up and running. No idea if it's device dependent or what.
Maybe @jam1388 or @vverve could test voice over wifi for you?

Just remember, before making your buying decision, that VoLTE is very much in beta and being worked on with Oneplus N10. It's not presently available on the Stable channel, and things break on the Daily builds.
I'm hopeful it'll make its way to Stable, but nobody's guaranteeing anything.

@oldbutndy I don't totally understand all the N10 versions (and I really tried at one point!) but Ruben, the porter/maintainer, has said that the T-Mobile / Metro versions should work, despite what the device page says. You'll find at least one other post in the N10 section of the forum that shows someone using an N10 Metro, in USA, who now has VoLTE.
I think no one wants to guaratee it, as it's not what the porter uses, but it sounds like it'll work.

I think Factory Unlocked generally just means it was never locked to a carrier, but doesn't mean bootloader is unlocked.
I found downgrading android, after unlocking the bootloader, to be a pain on the N10, but I'm pretty novice at that sorta stuff, and I got it done in the end.
Seek instructions, get the MSM tool, understand EDL mode. You'll figure it out!
Good luck!

@gpatel-fr It's really as simple as, if set to English (Canada):
Contact: +15145555555 will reliably be found by prediction once I type +151
Contact 15145554444 will not be found no matter what I type
Contact (514)555333 will not be found no matter what I type
Other contact formats (514) 555-5555, similarly won't be found. Nothing without the initial +.

Anyhow, I'm quite happy about the T9! Many thanks to you for making me aware of it, and for your help in diagnosing things. And many thanks to Lionel for creating the function!

My extensive (long-winded) testing was to try to be helpful, but I'm quite satisfied with how things function at present.
If the phone number predictions get improved for databases as mangled as mine, and various weird international standards, all the better! But sadly, I don't think I'm the person who will succeed with that.

The others phones that I know of:
Xiaomi Redmi Note 9 Pro - sounds like VoLTE is working for people, but band compatibility may not be perfect.
Xiaomi Poco X3 NFC - ""
Various Volla - ""
I've heard of people in USA using all three of these, but you really need to do your research and check with mobile providers.

Brax 3 has a UT port that's coming along. Applee has been in touch with them. It seems too early to say though, which is too bad, because they have a December shipment coming along.
Similarly Furiphone talked in the past of a UT port, but I haven't heard anything about it in a while. Both of those are explicitly made to work well in USA (among others).

Also Fairphone 4 is supposed to have working VoLTE now? There was an ebay seller in USA who was selling Fairphone 4 new. NeverMSRP I believe.

Ruben continues to work on VoLTE on the Oneplus Nord N10. Crossing fingers on that. Some people already have good results, but he's clear that it's still wonky so far.

@DJac @lduboeuf Just for extra confirmation, voice MMS works to and from Android for me, and I've just received a voice MMS successfully from a helpful iOS user. She couldn't listen to my message though, which I've run into before. Though I suspect if she downloaded and played in a separate audio player maybe?

Agreed that ability to download voice MMS would be a helpful feature.

@adorsaz Many of us on the forum may not know enough to have a well informed opinion on this. Certainly some devs hang around here, but many stick more to the various Ubuntu Touch Telegram groups.

For my part, I like the sound of what you're suggesting.. shared standards make a lot of sense to me. But I have absolutely no idea of the feasibility, and what the upsides and downsides for UT would be.
If you don't get more responses here, it could be worth asking on Telegram.

@gpatel-fr Owch. That doesn't sound like encouraging news about the database

For me, the plus is visible beneath the 0 in the dialer. A long press of the zero gives a plus sign.

Just to be clear, I had never tried to dial a plus sign before yesterday. I only tried it amongst a bunch of trial and error, testing to see what would trigger the phone number based predictions.
From what I read, yes, the + sign functions the same as the international call code, but I've never tried it. Could be region and/or carrier dependent.

One thing I find confusing is why, when set to either Canadian language, the tel_dom_fmt. Do you have any sense of what might be affected by this field? Our telephone standards here otherwise seem identical to USA, and it seems odd that the field should be empty when no others are.

@lduboeuf It does seem odd. I thought to try it because language settings also change 12 vs 24 hr clock (which is why I set myself to UK English in the first place). The results of locale -k LC_TELEPHONE change too, as per below.
If you do come back to this, my testing has been pretty thorough and I'm confident of what I stated, for Focal at least. Tested on both Oneplus Nord N10 20.04 OTA 11 and Oneplus 5, 20.04 (2025-W21). The only difference between the two was in what syntax would trigger predictions of phone number in France, when set to Français (France).. something about whether the 0 was included after the 33. I assume that was just a change in code over time, since my Oneplus 5 is 6+ months out of date.

@gpatel-fr It depends on language setting.
I get five lines of output, and am including the first four, as they all vary. Fourth just shows international dialing prefix changing as I change languages. Fifth always said "telephone-codeset="UTF-8"

While set to English (UK), which were my normal settings:
tel_int_fmt="+%c %a %l"
tel_dom_fmt="%A %l"
int_select="00"
int_prefix="44"

When I change language to Français (France):
tel_int_fmt="+%c %a %l"
tel_dom_fmt="%a %l"
int_select="00"
int_prefix="33"

English (Canada), and identically Français (Canada):
tel_int_fmt=""+%c %a %l"
tel_dom_fmt=""
int_select="011"
int_prefix="1"

English (USA)
tel_int_fmt="+%c (%a) %l"
tel_dom_fmt="(%a) %l"
int_select="11"
int_prefix="1"

Things like the capital A under English (UK), and the empty field under Canadian language settings aren't errors, I've checked and double checked this
(but I'd love to know how to copy and paste from UT Terminal )
All this should be replicable, but of course changing the language triggers a reboot, so it takes some time.