@bgriffis

in this case this seems indeed a network configuration problem. Maybe you could try to ask your provider, or search the Internet for web pages giving the appropriate parameters.

@bgriffis said in OnePlus 10 Nord on 24.04-1 (2026-01-17) - Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?:

Still no luck sending a picture

Note that the title of your post was 'could not fetch'. Not being able to send a MMS can be for another reason, that is, the image format not being supported by UT multimedia module. It's never the case if you use the integrated photo app to generate an image, of course, the image format is well-known.

@Vlad-Nirky said in Call for testing: Ubuntu Touch 24.04-1.2:

It was not only the ringtone, the contact shown in the phone call history

This I can't repro, I get the 'unknown' (from the contact list) calling number in the call list.

@Vlad-Nirky said in Call for testing: Ubuntu Touch 24.04-1.2:

an accidental glitch.

Hello

I don't think so. I did a quick test - calling from 2 different numbers, one with personalised ringtones and the other not registered in the contacts, heard only the same ringtone for both calls, so I can repro. I did not mention it myself as a regression because I did not even know that it was possible to play a personalised ringtone so I can't vouch that it worked correctly before.

@pparent

this could be linked to this change:

https://gitlab.com/ubports/development/core/packaging/maliit-framework/-/commit/6bd655621fea66af7b9bb3a477b9de072b4939db

if it is, you may find warnings such as 'Application attempted to activate itself without focus' in the journal.

@PhAndersson

there is no MR yet, it's for this issue

@bgriffis said in OnePlus 10 Nord on 24.04-1 (2026-01-17) - Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?:

Wifi is on

it's a well-known problem. The MMS providers are serving MMS in an insecure way, so do so only on their network. The fix is to have a special route for the MMS always going through cellular data.
There is this MR waiting to be reviewed.
While waiting for this change to get to stable, I have hacked a special route for my provider.

@bgriffis

I just tested it on my test setup and it works under 24.04-1.2RC1.

However, it seems that Dekko2 5.2 can get very upset about any error, for example not having
defined correctly the account and having made a mistake in the mail address of the person you want to send to. I made one and as soon as I clicked the mail languishing in Draft, dekko2 crashed indeed.

Check everything, once all is correct it should work. Note that I never use 'login' as authentication, always 'plain', and for my gmail account (not under Dekko2) I use port 587 with starttls.

@PhAndersson

how about setting up a public directory of what you have (if you have cleared the license question) ? It'll allow me to test it under Noble and possibly send a MR to gitlab once I'm sure that it works. Don't want to harass you of course, it's up to you to decide.

@peat_psuwit said in Call for testing: Ubuntu Touch 24.04-1.2:

To receive Ubuntu Touch 24.04-1.2 on a device running Ubuntu Touch 24.04-1.0, heads to System Settings -> Updates -> Update Settings -> Release Channel, then select "24.04-1.x Release candidate". Go back to the previous page, and then install the available update.

I was running 24.04-1.1 stable on my FP5 (are there people running 1.0 still ?) and selected update Ubuntu Touch, it installed the RC automatically without having to change channel. Restarted the phone without problem. Now disabling wifi, exiting settings, reentering settings and enabling wifi don't crash the phone, so it's clear progress without testing all the rest.

The most impressive app for UT, PureMaps in my opinion, works fine still, GPS works just as well (hum) as before, my ugly hack to start MorphQT6 when clicking a link works as before, my horrendous hack to run systemd-oomd works as before, phone works, my ugly hack to get MMS behind Wifi works as before, the fcitx keyboard works as before, the terminal works as before, installing an app from the store works as before, uWolf starts as before and the keyboard works, well I'll stop here it's a success so far, thanks to all devs for this great job !

Edit: I forgot to say that other things that were not working before on my phone still don't: fingerprint reader, disabling the developer mode still don't stay off when restarting the phone.

@danfro said in Signal UT: Signal-Desktop for Ubuntu Touch:

working with a config file:

Thanks for this hint, I stand corrected, I was thinking that settings in UT were done via a dbus mechanism covered by the gsettings interface - dbus allows to notify running applications of the change, an environment variable does not. So setting this value will not apply to running applications, leading to inconsistencies between applications if started before or after the change.

@mango

I'm not sure that @danfro's answer is painting a full picture.
In fact, I'd say that the main current development effort may bring accessibility improvements.

Most of the work around accessibility is not done by individual unpaid developers, but by professionnal devs working to develop the framework that the individual developers are widely using to help them. In the case of native UT applications, the framework is QT.

The bulk of the work done currently with UT is to upgrade the framework from QT5 to QT6.

Although this is done because QT5 is now obsolete and unsupported, this will bring the general improvements done in QT6 to support better accessibility. In your case, this means the flexbox layout that allows developers to design redimensioning interfaces more easily.

What you could do to help is reading about the works of people more advanced in accessibility with QT6 than UT, I mean KDE, and look at the things they have already done, because that's where the easier part to do is, and as such can be a beginning. Most enormous work has been done not in a mammoth project with big resources, but slowly over years. The important part is to actually begin. If the settings do not exist in the UI, it's not so important. What the UI does is mostly calling an interface to change the settings, gsettings, that can be also called from the command line. As UT relies on an existing distro, the APIs to set accessibility features may already exist. That don't mean that all will work automatically, but identifying what should work and don't is called bug searching. Once it's a bug, it can be added to the big TODO list (gitlab issues).

After all that, it's sure that devs will not work automatically on bugs that don't inspire them.
But something more meaty than a forum post could trigger some progress.

@danfro said in Signal UT: Signal-Desktop for Ubuntu Touch:

never saw the need to touch scaling, although I am wearing glasses.

err, huh, there is wearing glasses and, well, wearing glasses.

Most people wearing glasses have 10/10 after correction.

Some people are wearing glasses that are near the limit of what can be done realistically (2 cm thick glasses are not realist) and/or have specific problems (such as having one eye seing things a lot bigger than the other, so while both eyes look fine separately, the binocular vision is not so useful) that can't be fully corrected without risky surgery, so they don't have good vision despite glasses.

@mango

as far as I know Dekko2 is the only local client for UT. I don't use it but I tested it and with a few wrinkles (see issue) it seems to work. I don't see why Aol mail should be a problem since it seems to work with Imap/smtp.

@ma

the application was not open in the background as far as I know.
I did not configure anything for the app with TweakUT, I left the default value.
As far as I remember, when all of this was happening I was connected via wifi.
Restart: I stop the phone every day.

what I see looks very much like existing issues #179 and #183.

BTW whatever your problem is (you never described it), you can turn on debugging after installing dekko, starting it and closing it before setting up ,your account, go to the config directory under ~/.config/dekko2.dekkoproject and turn on debugging according to this procedure.

@Ida_

maybe you could give a try to the new alternative keyboard: fcitx5. It's a long shot to expect it to work better than the system one but you never know.

@Averiz

even with Min, it seems to happen only if prediction is turned off in fcitx-ub configuration.

@Averiz said in Fcitx-ub: a new keyboard for ubuntu touch:

Could you provide more information? I can't replicate this on my phone.

Yes, I could not repro it with Morph. However I can repro it every time with Min (min.pparent is a minimalist Chromium browser with OSK added with a hack, like for LibreWolf). I'd guess that's the only browser that can start with a truly blank page. I tried it again with the default system keyboard and the problem don't exist.

@Averiz said in Fcitx-ub: a new keyboard for ubuntu touch:

longer time on a more limited hardware
I
well, the FP5 with 8 Mb ram is one of the more powerful phones running UT. I just tested it again and it's taking about 5-6 seconds without any feedback before the display changes. Not a big problem, a bit disturbing.

@Averiz said in Fcitx-ub: a new keyboard for ubuntu touch:

could you try also restart fcitx?

the 'AZ' button now refuses to do anything. I selected an Azerty keyboard that displays in Qwerty

@Averiz said in Fcitx-ub: a new keyboard for ubuntu touch:

if you are willing to create issues

will do, I think that I will let the fcitx keyboard enabled and will test a bit more before doing so, though.

@Averiz

Congrats ! this is a great idea !

I tested it on my FP5 (24.04-1.1 stable) and it installed and restored the system keyboard. Needed to restart the phone but that's not important. Tested it with the terminal and a few browsers.

Good points:

1. I find it more pleasing to the eye that the system one.
2. It worked as well with alternate browsers (uWolf, Min) who have special methods to handle the keyboard.
3. with the terminal it does not interfer with the special input methods (double clic on the screen, special area

Minor points:

1. opening Min (an alternate browser) and Morph both with a blank initial screen, entering 'https:' and clicking on the blank screen generated a mad flickering of the keyboard and a Js error in the browser code (I took a screenshot but for some reason it's unreadable).

2. when setting / unsetting it as system keyboard there is some delay after clicking the button with no apparent feedback.

3. I (and I think most people) expected it to respect the system preferences for the language, nope, it's necessary to setup the keyboard in its own config screen. Yes, it's actually a high expection This config screen is not totally obvious by the way. I managed after a few mistakes to select the French Azerty as the default and it displayed finally - in Qwerty . I clicked on the 'AZ' key and it was Azerty finally.

4. after restoring the system OSK I set it again as the default, and I got back the qwerty with the french Azerty left selected, and this time clicking on AZ did not change the disposition, it stayed Qwerty.

5. still with the French Azerty, the text 'Keyboard - French - French (AZER) spills over the key ',' at the left (see screenshot)

Err, actually, I had closed the app without mercy while the validation was still spinning, I have opened it again today and... lo and behold ! all the mails were displayed. So it was just a problem of initial setup not validating for some (bad...) reason, while all parameters were correct.