Call for testing: Ubuntu Touch 24.04-1.1

gpatel-fr

I said in Call for testing: Ubuntu Touch 24.04-1.1:

no more hour from the network so I'm back in 1970

update: I have current date/hour again this morning, without doing anything.

When I installed 24.04.1 stable on 28 October, my phone started to display a current date in 11 July. I am not sure why (was it the date when the phone was built ?) It stayed this way (updating only the hour) even after I confirmed that the cellular phone was working by doing a successful call). After I enabled cellular data (why was it off by default ? maybe it was because I installed without SIM and added the SIM after install, but this should not happen in any case ?), my phone updated to current date. I assumed that it was getting the date from the cellular network, but it could just be from ntp in fact.

After that, I installed 24.04.1 daily, nothing to note from the date point of view. It was a new install after re-installing briefly Android to confirm some of the UT problems.

After updating the phone to RC according to the procedure in the topic, no more current date. The cellular data was on, the wifi was working, yet no date was set, I was still in 1970, only after disabling and enabling the wifi (this morning) could the phone get current date. I had noticed yesterday that I got failed attempts to update time through ntp in the system, but I had not thought it was important since I assumed that date sync was happening primarily through the cellular network.

I have again disabled the wifi, stopped and restarted the phone and yet the phone has the current date/hour. I have connected to the phone with adb shell and I have an initial time sync with ntp.ubuntu.com, so it has (I guess...) sync through the cellular data network, however in the log the date was correct before, so the current date has been kept and updated with an internal clock like it is done in a Pc. There are so many parameters, I am not sure of much now.

messayisto

@peat_psuwit Thanks for the Upgrade.
Notifications still don't work properly.
Telegram has none until I open the app . Then in the side launcher the number of received messages appear.
Cinny has none at all, though enabled in UT settings and in the app itself, nor has Dekko2.
Sms has none, too. Oops I just realize, that I don't receive sms at all. So this could be an isssue.
Device is Oneplus Nord 10.
I once tried to disable all notifications, then enabled them again, no difference.
Maybe @rubencarneiro as the porter is interested in this report as well.

messayisto

I can send sms but do not receice.

messayisto

https://dpaste.com/BWWCRHH7S

gpatel-fr

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

I can send sms but do not receice.

for me a quick sms receive test worked fine. It's on a FP5, but possibly a more important parameter is that where I am doing these tests, I don't have currently reliable access to 4 or 5G so it's down to 3G or LTE.

relevant parts of the log (with phone numbers masked by hand editing)

oct. 31 13:53:06 ubuntu-phablet ofonod[1824]: incoming sms, 30 bytes
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: tp-qt 0.9.8 DEBUG: Creating service::channelAdaptor for  Tp::DBusObject(0x557c21d4d0)
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: tp-qt 0.9.8 DEBUG: Interface "org.freedesktop.Telepathy.Channel.Type.Text" plugged
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: tp-qt 0.9.8 DEBUG: Interface "org.freedesktop.Telepathy.Channel.Interface.Messages" plugged
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: tp-qt 0.9.8 DEBUG: Interface "org.freedesktop.Telepathy.Channel.Interface.Group" plugged
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: oFonoConnection::inspectHandles contact (3, 2)
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: oFonoConnection::inspectHandles  ("+33783xxxxx", "+33782xxxxx")
oct. 31 13:53:06 ubuntu-phablet org.freedesktop.Telepathy.ConnectionManager.ofono[4207]: tp-qt 0.9.8 DEBUG: Interface "org.freedesktop.Telepathy.Channel.Interface.SMS" plugged

Looking at your log messages, I recognize some of them. I don't have any kind of messages such as:

The phone number is not a valid number:

or:

tp-qt 0.9.8 WARN: Call

did you have these messages before the upgrade ?

gpatel-fr

@peat_psuwit

automatic screen rotation does not work for me with RC (FP5)

In fairness, I have spent only 2 days with 24.04 stable and one day with 24.04 daily so I can't be 100% sure that rotation worked with daily. However I'm sure that it was working at least with stable.
I think that it was working with daily because it's something one notice very fast normally. And yes the setting 'rotation lock' is disabled and enabling/disabling it did not restore automatic screen rotation.

I did not look carefully in the sensor app at the gyroscope output so I'm not sure if something is wrong here - the changes are happening so fast that it's almost impossible to evaluate.

adorsaz

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.

vverve

@messayisto No 24.04-1.1 test , a simple note that with daily 24.01-1 it had the same random (after a few updates) problem ;
could send sms but do not receice on one+ n10 , switched to stable fix that, wont try rc for now. Still learning how to get those usefull error logs out to share it...i'll get there , and ,only got one device with ut for now . Thanks to all for UT .

gpatel-fr

I said in Call for testing: Ubuntu Touch 24.04-1.1:

automatic screen rotation does not work for me with RC (FP5)

oh well it's like a very bad movie.
a few minutes ago I found the phone black on my table, I had left it for a few minutes unattended. I expected to wake up by a single press on power button, but I had to press for at least 10 seconds to get a boot. When starting, the phone asked me for the wifi password (it was saved obviously). I declined and completed the boot, after wise I checked the wifi and it was connected with the saved password. In the logs the computer was back on 11 July, after that there was this message:

juil. 11 20:52:59 ubuntu-phablet systemd[1]: Finished snapd.apparmor.service - Load AppArmor profiles managed internally by snapd.
oct. 31 14:54:46 ubuntu-phablet systemd-timesyncd[1009]: System clock time unset or jumped backwards, restored from recorded timestamp: Fri 2025-10-31 14:54:46 CET

and then I noticed that automatic rotation was working again. Yuck.

Sms is still working for me in both directions though, so not all is lost

Edit: forgot to mention that battery is yet far above 50%

lazarus

@peat_psuwit Tried to install the 24.04-1.x channel release on my Sony Xperia X using the UBports installer. Installing was completed, but after reboot the device hangs at the white "Sony" screen for multiple minutes and won't boot any further.

Staying connected to the PC I can see the network connection established via USB, but I can't connect to 10.15.19.82 using ssh.

messayisto

@gpatel-fr Unfortunatly I dont know. Thanks for your help anyway!

messayisto

@lazarus Are you shure the device does support noble?

lazarus

No, I'm not, but it's listed here: https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-0-release-3973

messayisto

@lazarus Uhm, I see, but when I look here:
https://devices.ubuntu-touch.io/device/suzu/
its not listed. And not maintained, too. I tried myself to upgrade it to noble and failed the same way you did. So the two lists are confusing...

gandalf

I have a spare FP3+. Pressing the power button during boot (when Ubuntu Touch with the 5 dots is shown) crashes the phone. The screen turns off and doesn't come back. Pressing the power button again for 2-3 secs starts the normal power on cycle.

Swiping out of waydroid freezes the phone. Turning the screen off and on works, but it's otherwise unresponsive.

lduboeuf

@peat_psuwit
I think an update of Telegram is needed for the notifications list not cleared fix