Call for testing: Ubuntu Touch 24.04-1.1

messayisto

@gpatel-fr https://dpaste.com/2DPWCA7DB
there is only one entry saying that the phone number is not valid followed by the name of my provider.
Sorry, I am just a normal user, I cannot read logs. I do not know how to mask the telephone numbers as well...

messayisto

And these are the logs from the moment I switched back to stable.
https://dpaste.com/G5RUX2JBZ
Hope it helps.

gpatel-fr

@messayisto

I have seen this invalid number in my logs too, so I think it's just an invalid input in address management, nothing related to telephony by itself.

Keli

I updated from noble.stable and everything seems to be working here on lancelot.

Text messages now have a notification on the launcher!
Sms sending and receiving works on both sims including flash messages.
I can make calls on both lines.
Mobile data works - tested only with sim 1.
Push notifications work - I tested with DeltaTouch.
Camera works (Front and back, video and stills)
I haven't tested extensively so that's all I have for now.

lk108

@Keli said in Call for testing: Ubuntu Touch 24.04-1.1:

ush notifications work - I tested with DeltaTouch

However, clearing notifications does not work with DeltaTouch and 24.04-1.1 RC. We adapted to what we perceived as a change in the notifications DBus interface from focal to noble, but it seems this change is reverted in 24.04-1.1, so we need to revert as well, I assume.

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

The Teleports update should not be needed for this to be fixed, at least in the specific case of Teleports.

In xenial and focal, the clearPersistent DBus method of com.Lomiri.Postal required the appid and the tag as a string. In 24.04-1.0, the tag(s) had to be passed as array of strings. Is it correct that this has been reverted and tags are passed as strings instead of an array of strings to clearPersistent?

Keli

@lk108 said in Call for testing: Ubuntu Touch 24.04-1.1:

However, clearing notifications does not work with DeltaTouch and 24.04-1.1 RC.

Just tested this. I pushed the power button to turn my screen off, took another phone and sent myself random messages to my DeltaTouch, I heard the notification sounds and the screen turned itself on. I unlocked the phone and swiped down the screen to access the notifications indicator menu, I could see the Deltachat messages that I had sent to myself, I proceeded to click on the 'Clear all' button and said notifications were cleared. Is there something I'm missing?
I'm on 24.04-1.1 RC 1

lk108

@Keli It's not about the "Clear all" button, but about DeltaTouch removing the notification automatically, for example if you open a chat that contains the message for which a notification was sent.

Keli

@lk108 I see.. That makes sense now. Yes you are right, the notifications aren't automatically cleared after the messages are read.

peat_psuwit

@lk108 said in Call for testing: Ubuntu Touch 24.04-1.1:

In xenial and focal, the clearPersistent DBus method of com.Lomiri.Postal required the appid and the tag as a string. In 24.04-1.0, the tag(s) had to be passed as array of strings. Is it correct that this has been reverted and tags are passed as strings instead of an array of strings to clearPersistent?

That's sort-of correct. The change is "reverted" - more accurately, we made it so that the change seems to be reverted for applications which clear 1 tag at a time (which most applications do).

The full story is: originally, clearPersistent accepted not an appid and a tag, but an appid followed by an arbitrary amount of tags. Yes, for some reason, Canonical made the original clearPersistent accepts, for lack of better terms, "variadic arguments".

But this is very unusual in the DBus ecosystem. When we first migrated lomiri-push-service, a Go code, to the new DBus library (godbus/dbus), we didn't notice this weird pattern and assumed that the function accepted a list. Once we noticed this, we attempted to restore it, only to discover that it's not simple to support "variadic arguments" using godbus/dbus.

So we've decided on a compromise: we've discovered that, outside of our own code, most callers of clearPersistent pass only 1 tag to it. So, starting with 24.04-1.1, clearPersistent accepts exactly 1 appid and 1 tag, which should unbreak most unmodified applications. For those that actually pass multiple tags to clearPersistent, we now have clearPersistentList which accepts an appid followed by an array of tags.

"Technically", this DBus API is private and applications are supposed to use Lomiri.PushNotifications QML type. In practice, there are applications which need to call this DBus API from C++ or Rust. So we want to maintain compatibility where it makes sense.

This MR summarize the state of both functions in various versions of Ubuntu Touch, and also serves as an example on how one can support multiple versions of DBus methods.

Side note: I see in DeltaTouch codebase that you call QSysInfo::productVersion(). Please note that this function (currently) returns the version of the underlying Ubuntu version and not necessarily the version of Ubuntu Touch. With the new release scheme, we could have multiple Ubuntu Touch (major) versions be based on the same Ubuntu version. Please use other kinds of detections (such as what we outlined in the MR) instead.

peat_psuwit

@gpatel-fr said in Call for testing: Ubuntu Touch 24.04-1.1:

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

send file journal.log?

attached.
Note that I know why there are deny messages for ntp servers. It's the firewall on my installation (not ufw - a site firewall) blocking ntp for devices on wifi (these devices can only ping and https/https)
journal.log

Thank you for the log. While it gives me some information, unfortunately this log does not show the issue being reproduced. I'm going to include some changes in 24.04-1.2 which should makes this happen less often, but I won't be able to guarantee that it actually fixes the issue.

Since you mentioned NTP being blocked on your local network, it's probably worth mentioning that we currently don't use date & time given by cellular towers; the only way we can automatically set date & time is through NTP over either Wi-Fi or mobile data. Although in your case, I suspect that systemd-timesyncd (NTP client) doesn't react well with changing network conditions, which is why disabling and re-enabling mobile data doesn't help.

@adorsaz said in Call for testing: Ubuntu Touch 24.04-1.1:

On a Fairphone 4, I've migrated from daily build (19th October) to this RC, I confirm I am still able to use VoLTE to make a call.

Although I cannot send SMS to recipient with phone number formated with my country prefix (+41).
I share log here with redacted recipient phone number:

sms_send.log

Edit: during the day I was able to receive VoLTE call and receive SMS.

We're going to land a change that could help with this in tomorrow's 24.04-1.x daily image. If possible, please switch to 24.04-1.x daily channel and see if you can now send an SMS. If this is successful, we're going to have another RC image.

gpatel-fr

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

unfortunately this log does not show the issue being reproduced

yes it fixed itself without me doing anything for that. Looking at the systemd log files, I see that some are indeed dated from 1970 and some from July 2025 (I got the file at end of October), it's a bit difficult to make something from logs in this situation (not sure that journalctl is handling this well)

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

we currently don't use date & time given by cellular towers; the only way we can automatically set date & time is through NTP over either Wi-Fi or mobile data.

Ah thanks for clearing that point.
From the logs, when the phone is stopped, current date/hour is saved and restored at restart, so when the upgrade happened somehow this saved date was wiped out it seems. If one assumes that, problems in the mobile data (my place has variable cellular quality connexion) combined with the blocking of Ntp on my wifi network could explain that the phone was stuck in 1970 even after a restart. Eventually the phone got a cellular data connection and resyncronized its current data.

lk108

@peat_psuwit Thanks for the detailed explanation, very helpful! And the detection in the MR you linked is a piece of art.

adorsaz

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

We're going to land a change that could help with this in tomorrow's 24.04-1.x daily image. If possible, please switch to 24.04-1.x daily channel and see if you can now send an SMS. If this is successful, we're going to have another RC image.

I've installed the release "2025-11-04/3" from the daily channel and I was able to send SMS, thanks !

I've also checked again the SMS reception and VoLTE calls (sending and receiving): everything works well

messayisto

@adorsaz On my oneplus Nord 10 5g I am still not receiving sms neither on the latest rc nor on daily. I had to revert to stable. There its working. Did write that to the porter on telegram, too. Maybe device specific?

Carlos

This weekend I updated my Vollaphone22 from 24.04-1.0 to 24.04-1.1 and screen starts blinking on boot before the logo Ubuntu appears.
With installer reinstalled 24.04-1.1 without wiping data and everything I use every day starts working normally until I found a serious bug on calls.
Yesterday a friend calls me, I answered the call but no sound from other side. My friend repeated calling me and all answering was no sound.
With other phone at hand I search the source of the error and found the Vollaphone22 was the culprit.
How to reproduce is like this, make a call to other phone, wait that the other side answer the call, talk to test that audio is ok, wait that the other phone hang the call, now if you repeat process there is no sound if answered the call. Only rebooting Vollaphone works again, untill other phone terminates the call first and error returns.
This error does not happens on version 20.04 stable.