@gpatel-fr Yep, will definitely look out for network-related rings.

@gpatel-fr Your technical knowledge is greater than mine - I wouldn't know how to set up traces or look for sources of the issue without guidance. But if there are specific ways I can help test things out, let me know

@gandalf I can say that the first three items on your list do not occur for me on a Oneplus N10. I just tested to make sure. There are some times when it does seem to maybe get stuck reverting to 3G for calls (I now see an H in top indicator, for HSPA I guess) but WiFi doesn't trigger it for me.

@gpatel-fr I have also experienced the odd ring when dialing out since my OP N10 got VoLTE, but mostly not.
I thought maybe it was only occurring when I was connected over 3G, but no, after dialing some random 1-800 numbers it happens the same for a given number whether I'm on VoLTE or 3G/H.

I don't really see lack of ring as much of an issue (I'm still just amazed and grateful to have VoLTE!) but it's still worth trying to figure out when it does/doesn't happen. I'll start looking for whether its network dependent.

@tacofeast Yes, welcome!
It takes some considerable work to get Ubuntu Touch working on a given phone. There are no ports of Samsung phones at present, and porting is done by community members like yourself.
So to see UT running on those phones, you'd need to do the work, or find others interested in sharing that work. There's documentation on porting on the UBports website.

Alternately, there'd a list of already supported devices, and perhaps you could find one available used to test out the OS.

Has anybody had luck getting an unlock token from Oneplus for a BE2028 that was sold by a third party over amazon?
...
has anybody tried "adjusting" an invoice slightly?

@bunchy7s Note that the Oneplus 3 port isn't even listed on the main devices page. The page @moem dug up says that the last work on it was in 2021 and is for UT 16.04, which is quite out of date. And the video you followed is four years old.

I can't say that your issues are definitely caused by how out of date it is, but I can say that you're unlikely to have a good experience of Ubuntu Touch on that device.
Unless you want to take up the reins and bring the Oneplus 3 port up to date, I'd say your best bet to try UT is to read around on the forum and device pages and try to find a supported device that suits your needs and is affordable and available in your area.

Also of note: some people have difficulty with putting a phone back to android, so do your homework on that before attempting.. people have bricked their devices.

@chaosmaou VoLTE only landed on N10 in mid November, <4 months ago, so yes, it's worth trying again now that VoLTE is working.
Nobody is guaranteeing that it works perfectly / with all carriers, but so far results seem very good.

@rocket2nfinity I hadn't heard of a pending fix for group MMS. That's incredible news!

@lduboeuf This has been my experience using a Oneplus N10. Since VoLTE landed, idle drain has seemed notably less pronounced. A very nice surprise, especially on a device with an aged battery.

Very nice!

Non-EU users, note that Volla will sell outside the EU via an indiegogo page linked from their main site. The Plinius page presently links to a Quintus Indiegogo page, but I'm sure one is coming for the Plinius.
Seems they've been selling internationally this way for a while. I didn't know.
Not much is written about cell network compatibility, for those of us in nations where networks may require "whitelisting" for a device to be able to make calls, etc. But I blame the networks and a lack of government oversight for this more than I'd blame a company for not going and asking cell networks all over the world to whitelist them.
Anyway, as ever, you need to do your homework as to whether the device will work on a given network. Nice to buy from a company directly supporting and working with UBports!

@Kjetil Yes, sorry UB Connect is what I'm thinking of. Wasn't sure what all features were involved.
Hope you find something that fits your use!

Hmm. Perhaps wise to post here as well:
VoLTE working on Oneplus Nord N10, 20.04 OTA-12 RC-1.
Lucky Mobile under Bell network, Canada.
SMS working as normal.
MMS working as well or perhaps better than before. Fewer undownloadable messages, though this could yet be coincidence.

@Kjetil Somebody has made a version of KDEConnect for UT recently. I'm not sure it covers all your uses, and I think it's totally unconfined, so use at your own risk, but could be worth looking into.

@Fizz Somebody might know more than me, but my impression is that it might not be wise to count on VoLTE on Pixel 3a.
And yeah, 3G has gotten pretty patchy here, hasn't it.

Cheapest option, with best network coverage, is probably Oneplus Nord N10. VoLTE is working well for me on Lucky Mobile (Bell network). It's pretty new having VoLTE on this device. Huge cudos to Ruben, the maintainer.
There area few for sale on kijiji.
Most N10s here should be ok to unlock, but sometimes one of floats up here tied to a USA network, and with those you need an unlock token from Oneplus, which people are struggling to get, depending on if you have a receipt from an "official vendor".
The BE2026 models can just be unlocked, no fuss. Downgrading android is a bit tricky, but doable.

A couple Xiaomi phones have VoLTE - Poco X3 NFC and Redmi Note 9 Pro (and related Miatoll devices), but aren't ideal for Canadan network bands. I was trying to get a Redmi Note 9 Pro working, but to unlock bootloader, Xiaomi was requiring things that involved receiving short-code SMS, and they just wouldn't come through on any Canadian network. Multiple conversations with cell carriers and Xiaomi later, still can't get it unlocked.. and network coverage turned out to be kinda bad in my area.

I've heard of people using Fairphones in Canada. But usually can't find one except from overseas and it's a lot of money when the $%£$ networks won't guarantee they'll "whitelist it" and as such allow phone calls.

Other ports are coming along, but I guess the short of it is Oneplus N10 (or also N100, which lacks 5g) is your best bet.

All working well on 20.04 OTA-12 RC 1
Tested recurrent events, working hours, all day events, and fiddled around in general. All looks good!
Thanks for all your work Lionel!

@UBportsNews Plamen, of the Brax3 team, recently said that they were actively working with "the UT team" on the Brax3 port.
I thought UBports doesn't usually maintain device ports but maybe it's different when working with device manufacurers?

Is the port maintainer Brax3? UBports? A joint effort? Or is the hope that some individual will take on the port in the long run?

Thank you all!

@libremax Wow, nice bit of news! Thanks for sharing

@idonthatevests Interesting. For what it's worth, I'm very confident that mine was glitchy before I ever installed uFirefox. I did have Ambot Installer for the more limited Lomiri toolkit, but I'm not sure whether ithas anything to do with that.
Mine always seems to glitch out after notification/SMS.

I always kinda figured something about my install was messed up, though I did install what I thought was the appropriate firmware and do the whole MSM&EDL mode thing.

I mostly ignored this issue thinking that if it only affected my phone, it's not that important. But it'd be handy if we could pin it down.

@idonthatevests Does this glitch involve the screen flickering? Does it seem to occur in conjunction with incoming notifications/messages?
I don't have solutions, just have yet to encounter anyone with the same issue as me, and this sounds similar. Only the reboot to Fastboot saves me.

@shengchieh I would agree that Oneplus N10 best matches your specifications, and that the BE2026 version is your best bet for unlocking. This is assuming you are in USA, as I don't know of anywhere else where there's any talk of sunsetting 4G.

@bgriffis Hmm.. yeah, if WiFi being off didn't fix it, it's worth considering whether it's the two APN settings vs one setting thing. Plenty of folks have had it work one way but not the other - mostly I've heard of North Americans needing two separate settings.
For me in the past, MMS only worked if I had two APN settings AND the APN & MMSC for MMS did not match the APN & MMSC used for Internet. I got around this by finding a "tethering" APN for my carrier and using that as the Internet setting, and the normal APN for my MMS.

I still do get the same message as you, "Could not fetch...", for maybe 10 or 20% of incoming MMS messages, and clicking Download only yields a second (and third, and fourth..) such message. But if the I ask the sender to resend the same file, it generally does work the second time. I have never been able to figure out why this happens.