@messayisto in morph, whatismybrowser.com should say chromium 134 if you're on qt6, or chromium 87 if not

@larraine But even though you likely won't hear back, lots has improved in the past 3.5 years. Most people get MMS working more or less without issue, often just automatically. I wouldn't be too scared off by this thread.
Note that group messaging doesn't work, although there may be a fix coming, or even already implemented in the daily (not stable) builds.

Welcome to the community! Hope UT works out for you. It's a great OS and a great bunch of humans surrounding it

I don't know much about all this, so excuse me if I say stuff that doesn't make sense but could it be that 24.04 2.x has moved on with packaging Morph Qt 6 stuff, and the root partition isn't big enough on Oneplus N10? I believe its not on the list of devices that will get 24.04 2.0 (stable), at least for now, until somebody can figure out enlarging the partition.

@turtle_racer This is how it functioned on my old Oneplus One (R.I.P.), way back on 16.04 - alarms and I think also phone ringing would happen simultaneously through earphones and loudspeaker if earphones were plugged in.
I can see where one might not want it, but I found it a nice feature. I wouldn't know enough to say, but I suspect it was either the way that specific device port was made, or even something to do with the underlying firmware of that device.
I have no sense how hard/easy it might be to implement.

Glad to hear you're enjoying Ubuntu Touch so far. It's been my only smartphone OS ever, since late 2020, and I am continuously just wildly impressed with how good it is and how much it has improved.
Welcome to the community!

Well, moderators do have to make some decisions. To me it seemed @cibersheep made a polite request and also later apologized for the hiccup. This particular thread seems like a fine place to post about homespike, but I can't see which other posts were deleted.

To me it seemed like a fair instinct by a moderator, politely communicated, as well as fair points by @keneda.
Nothing so offputting to me.

@Vlad-Nirky Thanks for the reply! Yeah, my understanding is this generally works smoothly. I just wondered if my issue was a one-off, or uncommon but sometimes encountered.
I suspect my database is just screwed up somehow.
pragma integrity_check didn't find anything wrong, but that's as far as I got.
Anyway, not looking for support, just thought I should see if any others experienced something similar.

Congrats on your NP1! And 26.04, very cool!

Hi all,
Has anybody had issues after importing history.sqlite and the contents of history-service/attachments to a new device, to preserve message history and MMS files?
For me in past it has failed to load history for some contacts, but not others, and sometimes not allowed SMS to send, depending how I entered the Messages window with that individual. This can be entered through Notifications, by clicking on the most recent message from them in Messages, or by starting a new message in Messages and then typing their name in. Behaviour was different depending on which.

I never figured out why. I was always able to make something work by entering the message window via a different route, and over time the issue seemed to work itself out.

I ask because if others have had this issue, it's worth me trying to recreate it, save logs, report, etc. If I'm the only one, clearly a fringe case, and can be ignored.
Thanks

@aimar Excuse the slow reply.
I was trying to avoid updating too, as my device was already on the required Android version, but eventually when nothing else worked, I did upgrade. I still didn't get the SMS.

@pleoni I forgot that Whatsapp was given as an option, but that does seem familiar now.. perhaps this could be a solution?

Not that I want to get Whatsapp, but maybe I coils start an account with a cheap, temporary phone number just for unlocking the phone.

@aimar Yes, GMT + 8, and notably, that linked site confirms that it indeed resets at midnight in China, not some other time of day. Useful!

There's an excellent post to help install on Redmi Note 9 Pro and similar devices. While of course there will be differences for yours, like firmware, I strongly suspect the basics of unlocking will be the same.
The other difference is that the post is from 2024, and it seems clear that Xiaomi has made it harder to unlock. But at least this shows you the process:

https://forums.ubports.com/post/79264

@aimar Yeah, I'd read something about that. It resets at a certain time of day, China time (one big time zone).. not sure if it's midnight or what. Worth looking into what time the daily quota resets.

@aimar Thanks for the tip, and for posting that link! I'll try it out. Meanwhile my existing phone, Oneplus N10 got VoLTE support, and my need for a different phone evaporated.
But I'd love to get UT working on that device.

Good luck getting yours unlocked! Seems it may be more a question of luck than anything else

@aimar It should just be a one week (168 hour, they'll say) wait.

I can't confirm what @kln_nurv said exactly, but it does kinda fit with my experience.

I bought a Xiaomi Redmi Note 9 Pro from the EU for delivery in Canada. I made a Xiaomi account, synced it to the phone, waited 168 days, but where it failed was as part of something Xiaomi called SIM sync or something similar. There was supposed to be a verification SMS from Xiaomi. This would never be received, and SIM Sync / SIM Activation would fail.

Then when I'd try Mi Unlock Tool even after 7 days, it would say the phone isn't "Activated".
A few emails with Xiaomi and a couple calls with my cellular carrier later, I gave up.

The best they could come up with at the time is that "short-code SMS", the type commonly used for 2FA, wasn't coming through maybe because either Xiaomi didn't have servers in Canada, or because it wasn't in its original market. They said short-code SMS don't work internationally. None of this made very much sense to me.

So I dunno, it's possible it now only works from within China.
I still have the phone. I will try to find time to make a new Xiaomi account via a Proton VPN server in Hong Kong and see if that works.. best I can do.

Any recent reports from others unlocking Xiaomi devices could be helpful. This was in 2026 that I was trying. Clearly people succeeded at this in the past. But anybody done so this year?

@gpatel-fr So far it seems that reliably I will get a ring when calling somebody from the same network as me. From Lucky Mobile, in Canada, it rings when I call someone using Lucky Mobile or Virgin Mobile, both of which are MVNOs on the Bell Network.
I don't think I'm hearing any rings when not doing that. Calling 1-800 numbers yielded mixed results, but consistently it would ring or not ring for a given number.

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