Call for testing: Ubuntu Touch 24.04-1.0

danfro

On my OP5T battery drain is quite bad with noble 24.04-1.x RC2. From some ps aux checks, looks like one process is running at over 100%, so consuming more than one core constantly:
/usr/libexec/mediascanner-2.0/mediascanner-extractor

This is almost 4 hours after the last reboot. I do have around 5100 photos, a bit over 330 videos and about 300 songs.

journalctl -b | grep mediascanner
Sep 28 17:53:49 ubuntu-phablet systemd[3461]: Starting mediascanner-2.0.service - Media Scanner...
Sep 28 17:53:50 ubuntu-phablet systemd[3461]: Started mediascanner-2.0.service - Media Scanner.
Sep 28 17:53:50 ubuntu-phablet dbus-daemon[3541]: [session uid=32011 pid=3541] Activating service name='com.lomiri.MediaScanner2.Extractor' requested by ':1.21' (uid=32011 pid=4306 comm="/usr/bin/mediascanner-service-2.0" label="/usr/bin/mediascanner-service-2.0 (enforce)")
Sep 28 17:53:53 ubuntu-phablet mediascanner-se[4306]: No reply from extractor daemon, retrying once.
Sep 28 17:53:53 ubuntu-phablet dbus-daemon[3541]: [session uid=32011 pid=3541] Activating service name='com.lomiri.MediaScanner2.Extractor' requested by ':1.21' (uid=32011 pid=4306 comm="/usr/bin/mediascanner-service-2.0" label="/usr/bin/mediascanner-service-2.0 (enforce)")
Sep 28 17:53:54 ubuntu-phablet mediascanner-se[4306]: Error extracting from '/home/phablet/Videos/camera.ubports/video20250617_195550573.mp4': ExtractMetadata D-Bus call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Sep 28 17:53:54 ubuntu-phablet dbus-daemon[3541]: [session uid=32011 pid=3541] Activating service name='com.lomiri.MediaScanner2.Extractor' requested by ':1.21' (uid=32011 pid=4306 comm="/usr/bin/mediascanner-service-2.0" label="/usr/bin/mediascanner-service-2.0 (enforce)")
Sep 28 17:53:56 ubuntu-phablet mediascanner-se[4306]: No reply from extractor daemon, retrying once.
Sep 28 17:53:56 ubuntu-phablet dbus-daemon[3541]: [session uid=32011 pid=3541] Activating service name='com.lomiri.MediaScanner2.Extractor' requested by ':1.21' (uid=32011 pid=4306 comm="/usr/bin/mediascanner-service-2.0" label="/usr/bin/mediascanner-service-2.0 (enforce)")
Sep 28 17:53:59 ubuntu-phablet mediascanner-se[4306]: Error extracting from '/home/phablet/Videos/camera.ubports/video20250531_204017129.mp4': ExtractMetadata D-Bus call failed: GDBus.Error:com.lomiri.MediaScanner2.Error.Failed: Unable to discover file /home/phablet/Videos/camera.ubports/video20250531_204017129.mp4
Sep 28 17:54:26 ubuntu-phablet mediascanner-se[4306]: Error extracting from '/home/phablet/Videos/camera.ubports/video20230712_192905493.mp4': ExtractMetadata D-Bus call failed: Timeout was reached
Sep 28 17:54:51 ubuntu-phablet mediascanner-se[4306]: Error extracting from '/home/phablet/Videos/camera.ubports/video20240611_193555237.mp4': ExtractMetadata D-Bus call failed: Timeout was reached

and some more lines like the last ones.

peat_psuwit

Update 30 September 2025: after debugging, we've decided that it's likely that the report where some devices fail to boot after installing Ubuntu Touch 24.04-1.0 RC 2 is likely a false positive. As such, it's been decided to go ahead with the release of 24.04-1.0.

Which means that Ubuntu Touch 24.04-1.0 is now released.

https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-0-release-3973

Thank you for everyone involved in testing.

Keneda

@peat_psuwit
This is the first stable release for 24.04, if I understand correctly ?

It's known that fingerprint sensor on Fairphone 5 does not always work.

Well, there even is a "sensorgate" as this capricious sensor can cause the device to brick after android 15 update if it dies !

Thanks to you and all the Devs involved in releasing this great OS to the people

Opolork

I want to give a big thanks to all those that make Ubuntu Touch possible.

ma

Yesterday I received the update. After restarting, the phone gets stuck on the startup screen (Android logo). What can I do? Thanks.

Moem

@ma said in Call for testing: Ubuntu Touch 24.04-1.0:

After restarting, the phone gets stuck on the startup screen (Android logo).

How long did you wait? First boot after upgrading can take considerable time.

danfro

@ma You could try installing via the installer.

danfro

@Moem True. I found it can take several minutes on logo screen. So give it ten minutes.

ma

@danfro After a long wait, the Ubuntu Touch boot screen appeared yesterday, followed by the unlock screen. However, the phone could not be unlocked. So, I restarted it by pressing the power button. Then the Android screen appeared, and I waited for about 8 hours.

When I press the power button again and restart the phone, it remains stuck on the Android screen without any changes.

kugiigi

Hopefully, we will still get the separate announcement/post about the long wait after the upgrade so that less people will be confused

danfro

@kugiigi I posted some messages in our main groups. Not sure if an official announcment will be made

danfro

@ma so if you saw the unlock screen, it kind did install. But obviously something went wrong. I haven't heard of such a case before.

I suggest using the installer and reinstall. Do NOT tick wipe, that will keep all your data.

ma

@danfro I was finally able to install the update using the Ubports Installer. However, I also received a message here that an error occurred. I chose the "Ignore" option, and the update was installed—hopefully without errors.

Thank you for your support!

danfro

@ma Glad it worked so far. But might be worth giving information about that behaviour and the error message to the porter(s) of your device. Sometjing may need fixing.