@oldbutndy In Ubuntu Touch, all "About This Device" tells me is "OneplusN10". Looking up IMEI didn't yield anything specific about model #.

My best guess after some reading on XDA:
BE2025=Metro(USA?)
BE2026=North America, non-network
BE2028=TMobile(USA?)
BE2029=Global except stupid North American market?

Anyway, mine does NOT have a dual SIM, and I never saw Metro or T-Mobile on boot, so I presume it's BE2026. Happy to check further if you know how.
But sounds like BE2026 (if you can get your hands on it) or non-eBay purchase is the way to go?

Thanks for the info about them asking for sales receipts, BTW.. I'm considering buying a replacement N10 for my poor broken old one, now that VoLTE seems to be coming along. 3G is slowly being sunset up here in Canada too.
I've been trying to get a Redmi Note 9 Pro working, but can't get bootloader unlocked, and network coverage isn't great anyway.

I can confirm that I have unlocked a OP N10 without a code. Bought in Canada, not sold by a telecom. I think it was probably BE2026?

What I don't understand is how Oneplus knows the phone was from eBay. Did you mention that in applying for a code to unlock the bootloader?

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

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!