@naizena It might still be worth considering a wireless display option if it's important to you. I'm sure wired is a better solution, but if not possible, it's nice to have another option.
I was going to suggest the Microsoft Miracast Adapter V2, which has worked very well for me with several different UT devices.. but it seems the adapter is no longer produced and it's hard to find a used one.

Does anybody know of any other wireless display adapters that work well?

Mine wasn't cheap, $60 CAD (€40), but if using an external display is an important feature to you, it's a shame not to be able to. I get minor latency in display (well under 0.5 seconds), and two-finger scrolling doesn't always work when using the phone screen as a mouse. But with a Bluetooth keyboard and mouse, it's great. And while not every app is well set up for it, on the whole the OS functions very well in desktop mode.
I hope you're able to find a solution.

@rubencarneiro Thanks for the tip! I had meanwhile procured a global version and have been daily driving it for a few weeks. Works great! Thanks sincerely for all your work.

I'll probably still convert the TMobile one.. even if I sell it, good to have more phones out there running UT.

Oh, interesting. So many folks haven't read through and followed the initial steps that I thought it made sense to mention.
But I'm out of ideas. I wonder if any others have the same experience.

If you do re-install, use the best USB cord you've got - that seems to often be an issue.

Hi @kuzmi4,
Hopefully you're aware that the ReadMe linked from the Gitlab page for this port says only certain models/firmware are supported? I had missed that when I started looking at this phone for UT. Sounds like yours is maybe an unsupported USA based T-Mobile/Metro version?
That said, it seems like others may have had luck with the T-Mobile and Metro versions of the phone.

Did you revert to the 10.5.7 or 10.5.8 firmware before installing UT? And if so, are you sure the firmware was for BE2028 and not BE2029? I wonder if installing the different firmware would change how it reads the device.
My BE2026 seems to read correctly, for reference.

I don't know how much, if at all, these things matter. Just trying to help with what I know.
Best I can tell, BE2028 are American network specific and have different firmware editions ending in 8. The ReadMe links to supported EU and Global firmwares ending in 9 and 6 respectively, although I wonder if these may actually correspond to the Global (BE2029) and North American (BE2026) phone editions, based on reading other websites?

In any case, welcome to the forum, and I'm glad your phone works!

@jam1388 Thanks for the reply and the info!
I wound up finding a Global edition (BE2026) in a nearby city that I was visiting. I'll probably return the Verizon one, although your success makes me curious to try.
We've still got 3G up here for another year or so. I've been feeling for UT users south of the border. More and more nations are shutting down 2G and 3G. I've followed this issue for quite some time as a non-dev, and in short, it's just really hard to solve. They've made some amazing progress.
If systems like VoLTE had been set up based on open, international standards, I think it's safe to say it would've been solved long ago. Meanwhile, yep, heros is the right word for all the devs.
Anyway, thanks for your reply. So far the port's working perfectly!

@jam1388 Have you continued using this phone? Any further report on functionality?
Your issue with the phone not automatically switching between 4G and 2G is indeed not normal.. both my past UT phones have done that fine. Maybe it's somehow a result of incorrect firmware?

I'm asking for any reports you deem relevant especially because I just bought an OP N10 online that turned out to be an unlocked T-Mobile version (they aren't even a carrier here in Canada). Trying to decide if it's worth trying on 10.5.8, but the need to manually switch between 4G mode and back would already a major drawback for me.

I may be able to return this phone for a short window, so any feedback on functionality (aside from UT-wide issues) is welcome.

@Bunchy are you still around the forum? Did you have success downgrading?
I've just bought an N10 that turned out to be from T-Mobile (didn't expect this, as it's not a carrier where I live), and am debating whether I need to return it.

The readme that @rubencarneiro mentions (and authored - many thanks!) says the T-Mobile firmware 10.5.8 version, BE88CB, is unsupported.
I presume the whole device is an issue, and that it's probably a bad idea to try to downgrade my T-Mobile phone to the Global BE88AA 10.5.7 firmware?

It may still be possible for me to return this phone and hope to find a Global version.

Thanks for posting, that's interesting.
It mentioned it'd be a Mediatek device, which if I understand correctly sounds like a better candidate for VoLTE.. IF the device arrives and IF the port works, etc.

In any case, a nice bit of publicity. I figure more publicity, more users, perhaps more developers and also more donations to the foundation

Look forward to hearing more as things develop @Lakotaubp. Thanks!

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!

Thanks a million to whoever fixed this so quickly! And for updating the core system apps in general. We appreciate you!

Many thanks, team! Installed as normal on Oneplus 5T.

@peat_psuwit Thanks for clarifying. I hadn't figured that out from reading through the issue. Just wanted to make sure it was known.
Keep up the good work! Thank you

This is a little off where the topic has gotten to, but a quick note:
MMS has always worked independently of wifi on/off for me. On Oneplus 1, 5, and 5T, 16.04 and 20.04, MMS sends and receives with wifi connected. I've heard some others say the same on the forum.

2024-W45 is working just fine for me on a Oneplus 5. SMS, MMS, data, vibration and wireless display via Miracast all working as normal.

Thanks as ever to the devs for their hard 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!

Well, I'm glad you have a fix, but it sure sounds painful. Wish someone had been able to find a simpler way.
Hopefully this thread at least helps others with similar issues.

@ezst036 Sorry to hear those things haven't worked. I assume that if restarting nuntium didn't fix the problem, it's just a different issue than I was having.

I hope you're able to resolve it somehow without a full backup and re-install. I presume that in the past when this has happened to you, flashing without wiping data didn't fix the issue?

@arubislander
That's a really helpful tip, for me and no doubt for others. Thanks a lot!

@ezst036 Can I ask what device you're using? Mine's a Oneplus 5/5T. It did seem like a number of other people had struggles with MMS on these devices, including some where it worked and then would suddenly stop working.

In case it's useful, here's what I used to do before I found the nuntium command. I have no idea whether it's all needed, but this fix also worked reliably, the restart nuntium command was just a lot faster.

"I have a weird process that fixes it, some of which is probably unnecessary/superstition: I change my MMS APN to something incorrect, disable MMS, restart phone, correct the MMS APN, enable MMS again, restart phone again, and then it works."

full post in
in https://forums.ubports.com/topic/8145/mms-status-on-the-oneplus-5-cheeseburger/3

@ezst036

Except, when I type in that command or just when I type in initctl I get:

bash: initctl: command not found

Whoops indeed. Looks like that command doesn't exist in 20.04. Sorry for the bad advice, I'm still running 16.04 on my daily driver, as I have some need for video calls.
I wonder if there's a way to get that command back. After a quick bit of searching I tried "apt-install upstart" without success.

wouldn't this nuntium be restarted if I do a phone shutdown or reboot?

I would have thought so too, but I had this problem many times, far more often than once every six months. Restarting/shutting down never fixed it, and that command always did.

I lack technical knowledge, and really just poked at things a bunch without always understanding. Lionel knows 1000 times more than me and has actually worked on a bunch of this stuff, so please defer to his advice over mine. I just happen to have had the same (or a similar sounding) issue as you.
Before I discovered that terminal command, I did have a more convoluted fix, which I'll go look for.

Here's something to try. I can't say whether it will definitely fix things, but it's quick and it won't break anything.

Open Terminal
type "initctl --user restart nuntium"

It should return something like "nuntium start/running, process " and then a short string of digits.

I used to have an identical sounding issue, occurring unpredictably, every so often. Wheel spinning forever on outgoing MMS, nothing to indicate an incoming MMS even happened. For me the above fix always worked.
I never figured out what made the problem happen, or how to know when it HAD happened besides manually testing. I always worried a client had texted me without me knowing.
It hasn't happened since I changed cell providers, and it's now been long enough that I think it just doesn't happen any more.

This may be provider specific, but I'm able to text photos to myself, which was always a good test of whether or not things were working.