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

Excellent project, many thanks to Marius and all others involved!

Priority 2:
-RCS: lacking RCS isn't a bug exactly. But where I live it's a missing part of core phone functionality at this point, especially when UT's MMS lacks Group Messages and (for me, across devices) has always missed some messages outright. This is the single biggest reason I haven't gotten anyone to switch to UT here in Canada. MMS/RCS is an expected baseline way to communicate in Canada and USA, and increasingly RCS is ubiquitous. It's a much bigger problem now that iOS and Android talk to each other smoothly, as people expect you've seen their message, and you don't know anything was sent.
But that's probably a big task, and I know this isn't a big issue in lots of the world.

Priority 3:
-Autocorrect: I may be in the minority, but I've always used autocorrect in UT. I've heard it dismissed in Q&As as not worth using, but it's really not that bad, and I think a lot of new users expect decent autocorrect. I wouldn't expect it to get to the level of android/iOS with context-dependent editing, but fixing a few bugs that I'm long since accustomed to would make the existing UT autocorrect pretty decent. Happy to chat in greater detail about specifics.

-Screen flicker during calls: on Oneplus 1, Oneplus 5, and Oneplus N10, 16.04 and 20.04, when on a phone call the screen will sort of flicker off and on, making it difficult to use anything else while on a call, and sometimes also hard to shut the screen off. I have not yet tried 24.04.

-GPS crashes/freezes navigation apps: this occurs in Morph, uNav, and Puremaps in different ways for different users. Most of us have some workaround, but it'd be a very nice bug (or set of bugs) to have fixed.

Priority 4:
-Notches and Rounded Corners

Priority 5:
-AGPS
-Backup/Restore: some native OS way to handle this, including backing up data from apps that store your work outside the normal home folder, like Recorder.

Thanks a million to the developers who're working on this. I really think this is exactly the sort of effort that could grow the userbase, which leads to more devs, more donations, and as such more progress in a positive feedback loop

@lduboeuf Aha! I've gotten somewhere. In short, it relates to what language my system is set to.

I was suspecting some sort of regional dialing syntax issue. I tried changing my location in System Settings, to no effect. Then I tried changing my language to Français (France), and sure enough, up comes the cidrerie after dialing +33029, or also after dialing 029.
Attempting to dial Canadian numbers while set to Français (France) didn't yield any predictions regardless of syntax.

It only then occurred to me that my language is normally set to English (UK), not English (Canada). Setting it to English (Canada), I CAN get certain contacts to be predicted, but only if I start by dialing +1, and only then for contacts that happen to have the number saved starting with +1. My Contacts seem to have a wide variety of snytaxes, some starting in +1, others simply with 1, others without the regional code at all. Also some using parentheses, some not. Perhaps this relates to a Contact list that has been exported from one device to another and from 16.04 to 20.04, with different contacts being added at different times. The contact list has always been within UT.

I have never dialed a plus sign, living here. Using Google Maps, if I set my VPN to Canada, I see (555) 555-5555, where if set to, for example, France and searching a Canadian business I see +1 555-555-5555.
So in short, even with my language set to Canadian English, I wouldn't have stumbled across any predictions based on phone numbers. It only works for numbers stored with a +, and only if I type the + when dialing.

If it weren't too complicated a change, perhaps if the numeric prediction search dropped all special characters like + and (, it would work more internationally? But I have no idea how feasible this is.
The predictions based on contact name are probably useful to a lot more people anyway, and I don't want to create more work for you. Just trying to be helpful in the small ways that I can by testing and reporting.

@gpatel-fr said in Tip: call a contact with one hand (secret UT key !):

Version: 1.0.0+0~20241101095734.1+ubports20.04~1.gbpe21919

I do get this exact output for version number as output to the grep command you gave. But my assumption, based on Lionel not mentioning the version, and based on the fact that I do see suggestions based on contact name, is that this was all introduced before 24.04.

@lduboeuf Your development time is valuable! Maybe let me ask around a bit first on Matrix/Telegram for other people to test and make sure it's not just me before you go spending time digging into it.
I have now tested on a broken old Oneplus 5 too, and it's the same for me there- perfect predictions based on T9 spelling contact names, but no predictions based on phone number.

@lduboeuf Pardon my miscommunication! I only thought the predictions were bad when I didn't understand that the T9 element was happening, and they seemed to come out of nowhere and not relate to anything. A laugh solely at my own ignorance

But I don't get any predictions based on phone number, whether I use the region prefix or not. All predictions that I see are T9 based.
Once I have entered the full phone number of a contact in the dialer, it displays the contact name. But that's clearly a different feature, as the contact name does not appear in a box like it does with predictions.
I can type all but the final digit, with or without regional code, without seeing a prediction based on phone number.
I thought it might relate to parentheses in phone numbers as displayed in Contacts, which is a regional custom here, but I've found contacts without parentheses and these don't come up either.
I've also just tried adding a nice Ciderie de Bretagne as a contact, rebooting, and dialing the number, both with and without the 33 - still no prediction based on number.

Oneplus Nord N10, 20.04 OTA 11, Canada.

In any case, i love this T9 feature. Thank you!!

@kugiigi Thank you for your work on the redisgned app, by the way! Look forward to trying it when I make the switch to Noble!

@kugiigi Wow! T9!
As somebody who still often "dials" a phone number, I always just figured those contact names that appeared as I started dialing were predictions based on the phone number.. but pretty bad predictions
Finally I understand! That seems like a really useful feature!
(also, I think T9 WAS the one where you only had to press each number a single time.)

Kugiigi, it seems you did not create the (perhaps handy) bug. I have it in Focal, it's just in a different place - in line with where dialed numbers appear, left hand side. Again, it's the same place Create New Contact button will appear once something is dialed.

@fair I think maybe I commented in another thread where you said similar things, but have you tried adjusting things in UT Tweak Tool under Edge Sensitivity?
I was using one hand while I read your post. For reading, selecting between apps, opening new apps, one hand is natural for me and I never really thought about it. My fingers along the back of the phone maybe change position a little to reach the far side with my thumb.
Sometimes a clunky phone case maybe makes it more difficult? But that's where adjusting edge swipe width comes in.

Anyway, no need to use UT if it doesn't suit you. Hopefully Mir 2 will allow easier desktop app integration and the usable app ecosystem will expand in coming years, but we can't force companies, banks, etc. to make UT apps. I'm lucky that much of what I need to do can be done with websites (even banking).

I hope you find what you're looking for, and in the end if you have the time and are able to introduce some of the things you want into UT, I'm sure you won't be the only one who wants them, and it will be appreciated!

Maybe this is the wrong place to post this now that 20.04 OTA-11 is already released. If so, pardon me, I'll happily start a new post.

Thanks to the team for another Focal release! Unfortunately I have lost the ability to receive SMS since updating to OTA-11 last night. Outgoing SMS works as normal. I've tried rebooting, powering off, etc.
I'm using a Oneplus Nord N10, and was updating from OTA-10. VoLTE is not (and can not be) enabled.

Both incoming and outgoing MMS also don't work, and while sometimes glitchy, these normally work for me too. I've tried restarting nuntium.service, which normally fixes things if MMS fail to arrive with no notification, as they presently are, but it's not changing anything here.

I've also now re-flashed the system, again on 20.04 OTA-11, and no change.
Having trouble finding anything relevant under Logviewer - Messages.
Any suggestions appreciated.

Also, while I'm replying here, I was sorry to hear about the flooding @peat_psuwit, that sounded like a major storm. Thanks for all you do for UT!

@vverve said in VOLTE status:

Did not saw any signs of a 5G here passing some said as well covered area....

I don't think Fizz provides 5G under any of their plans.

Thank you both for reporting on your tests!

@jam1388 said in VOLTE status:

it has to be 25.04.2x daily for anyone wanting to make calls anyways on the nord n10

Just to clarify for other readers, theabove is true if 3G has already been shut down where you live. N10 works fine on 3G (and 2G).

Thanks for your report @jam1388. Very good news!