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

Pure Maps, " Slim and " Unconfined are all available in the OpenStore as viewed from 20.04 again.
Thanks Jonatan!

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.

@DJac Yep! If you want, you could scroll to top, click the gear icon near the blue reply button, Mark as a Question, then Mark as Solved. Helps with forum tidiness.

@UBportsNews What is meant by "Supportive Member" as opposed to "Free Member" when signing up to help with Writing, Testing, etc?
Is signing up under the Get Involved section of the website still a good way to go about joining these teams? It hasn't worked the past couple times I've tried.

Thanks for keeping us informed and entertained!

Pure Maps, " Slim and " Unconfined are all available in the OpenStore as viewed from 20.04 again.
Thanks Jonatan!

@DJac Version 3.1.0 was for Xenial, 16.04. You need to use a newer version for Focal, 20.04. I'd uninstall the other one first if I were you.

I did mention this for you on the Matrix channel I mentioned above and Jonatan was unaware that it had disappeared, so perhaps it'll reappear in the OpenStore for those on 20.04 soon.

@HarryBass Hmm. I don't have any great answers, but a couple ideas.
First, please state what version of UT you're using (20.04 OTA__ / 24.04___), it could help others assist you.

This thread is mostly about MMS issues, but at one point the user describes losing SMS messages as well. After a few days of SMS not working, it seems that the Terminal command sudo systemctl restart ofono caused a bunch of undelivered messages to come streaming in.
The poster has not described whether they rebooted during the time that SMS wasn't working, but I'd suspect that one would've tried that at some point, and that for some reason the restart ofono command did something that a reboot did not.

Receiving SMS half the time seems different, but I thought I'd provide what I could.
I have what seems to be unique issues with my OP N10, which also involves undelivered SMS, but if a flickering screen upon shutdown/reboot happens to you, let me know.

@DJac There you go, you should be able to install from Bolly's link. You'll want one of the arm64 builds.
Still not clear exactly why it's not visible in the Openstore from a 20.04 device. Did you contact anyone?

@garsbenjoe Please note that this thread has been inactive for 4 years before one recent comment. Also, I think vertical scrolling doesn't work well in desktop mode across the board, not just in Morph, and is a known issue.
Thanks for your input though!

@gpatel-fr Thank you for the explanation. Slowly, very slowly, I learn more about the technical end of things.
If indeed it was SMS that came flooding in after ofono was restarted, it makes me wonder if they had tried rebooting the phone prior to that, during the three days that they were unable to receive SMS.

@gpatel-fr Ah, I understand your interpretation, but I think the flood of "plain text messages" to which they're referring is not logs, but a bunch of undelivered SMS which suddenly were all delivered at once after the daemon and ofono restarted.
They go on to talk about the dating of the messages and reference "text messages", which generally means SMS.
I think they're saying that the SMS timestamps were all from right then, when the SMS were delivered, which is how UT lists timestamps in Messages (although under Notifications one can see the time at which an SMS was actually sent).

@ezst036 Can you clarify whether by flood of plain text messages you mean logs or SMS?

@gpatel-fr Thanks for the help! I don't have the MMS issue anymore, so can't provide logs. There's history of this in the forum, going back to when it was an initctl command under 16.04. In another thread Lionel theorized that perhaps nuntium was being started too early in the boot process, but again nobody provided logs. I tried to recreate the issue on a broken old phone just for the logs, but failed.

Thanks for the clarification on the other commands. The reason I was hopeful it might fix my situation was having read:
@ezst036 said in How can I troubleshoot broken SMS?:

Interesting. As soon as I restarted the daemon with 'sudo systemctl daemon-reload' and 'sudo systemctl restart ofono', a flood of plain text messages instantly came in.

I really appreciate people looking for the root of an issue like you are, and recognize that even if the restart-nuntium command works, it's a quick fix that doesn't help anyone solve any underlying bugs unless logs can be provided.