@vverve This number is the daily build for your specific device. All devices have their own number, since some changes may only affect one or few devices, but not all. So one device may get a build, others not. Some core changes may affect all devices, so all get a new build.

With a couple of hundred repositories its surely hard to track changes, but for tracking changes I am looking at merged MR's: https://gitlab.com/groups/ubports/development/core/-/merge_requests?scope=all&state=merged

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

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

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

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

@ma You could try installing via the installer.

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.

Hi, just want to let you know, that I managed to make the newer Cinny version to work with our old morph Webengine. This took downgrading of matrix-dsk and some patching. The RC for Cinny UT based on Cinny 4.10.0 can be downloaded here https://github.com/Danfro/cinny-ut/releases.
I made releases for focal (.1RC) and for noble (.nRC).

Here it seems to work fine, please let me know if you hit any new issues. I know, we still have plenty of old issues.

@ikoz ah, background color. That could be too. With flickable I think, I couldn't get flicking flickable and scrolling in the TextArea get working since both use the touch events. Yeah, not that easy. Its not that I didn't try.

@domubpkm This is more for the "human eye". The file will be simple text regardless of the extension. But I think this is safer also when sharing to other apps since they can use the extension.

But I agree, I should simply add the extension without bothering the user with this checkbox.

@ikoz Have you tried it with a large text in a TextArea? Its too long ago to remember details, but I tried that and decided this won't be a good solution. I think scrolling or so was not possible or some other restriction. Some users do have multi page text, so that would need to be handled.

Its not that I am against it. If we can make that usable I won't mind. Maybe I did something wrong when trying.

@ikoz Because text doesn't allow scrolling and pan, webview does. The whole handling of long documents is not easy and would need to be added manually. So a webview is an easy out-of-the-box solution. Not perfect, sure.

@domubpkm tedit uses .txt for all files stored. That should have been there all the time. Is there some different behaviour now than before?

No, the link would only be clickable if you would wrap it in proper html tags. See here: https://www.w3schools.com/html/html_links.asp

I will try to see if I can improve the copy option, but that is our morph/webview implementation. Should be the same in your browser.

@domubpkm Please try this build. https://gitlab.com/Danfro/tedit/-/jobs/10912582472/artifacts/raw/build/aarch64-linux-gnu/app/tedit.danfro_3.5.1.1_arm64.click

I did increase the version number. This might be needed for the device to pick up the apparmor change. I had to add "webview" permission there.

@domubpkm I finally found my mistake and managed to implement a read-only mode using a webview. Can you (and anyone else of course) please test this new build: link (use link below)

It might not be the most fancy way of doing it, but it seems to work. Since the text is shown in html, if you do use common html tags like <b>bold text</b> they should be displayed. Yes, that means if you do bother copying links with the full html link tag, they should be clickable as well.

@mschmids Since some changes in mattix sdk cause the problems, it may well be that element web faces the same issues as cinny, because it likey uses that as well. Just a guess, though.

@wally Correct, Cinny does work on focal very well. But right now, we will not have newer Cinny features.

If I find some time, I will try to do some UT-only bug fixes. And I will keep trying to look into making the newer version to work on UT.

@AppLee Sadly this is true. Cinny 4.7.0, 4.7.1 and 4.8.0 have been released. But they bumped matrix sdk, which makes the app only throw an error (as web app in morph the same). I didn't find a way yet to make it work with our Webengine (I tried with every release). I will try our dev group when I find time, but in worst case we will need to wait for a newer browser until we can have more cinny updates.

Oh, sorry, just saw that you are still on xenial. There is no xenial version of cinny-ut and there will not be one (at least not done by me).

@mschmids Better try cinny-ut from OpenStore, which is a much newer version.