@gpatel-fr We certainly can als use gsettings. I made a proof of concept for ThemeSwitch app a while ago (https://gitlab.com/Danfro/themeswitch/-/tree/gsetting_focal?ref_type=heads).

I am almost sure we can't use other apps values without loosing confinement. The value would need to be provided by the system. I guess if GRID_UNIT_PX could be changed in system settings and apps read that, that might work. Or it may need another apparmor rule. But I am really not that knowledgable to answer all details.

@gpatel-fr I do admit, I didn't look into Qt6 yet. Maybe that will bring us ways to improve. And you are right, since we use components like Qt or Ubuntu, there are professionals working on that. But it still needs people to make use of it in UT.

@pparent Looks like its somehow working with a config file: https://gitlab.com/myii/ut-tweak-tool/-/blob/master/src/app/qml/behaviourTab/LomiriScaling.qml?ref_type=heads#L32

@mango I remember discussions from TG groups every now and then. And @pparent I am sorry if my comment about glasses was misleading. I didn't wanted to be disrespectful for people with reduced sight.

The qml code does in theory allow to use relative text sizes. See: https://ubports.gitlab.io/docs/api-docs/index.html?p=lomiriuserinterfacetoolkit%2Fqml-lomiri-components-label.html
I think this might even be a Lomiri adjustment, because I don't see textSize property in normal Qt Label.
Maybe we should bring up this topic into develompent groups again.

But for instance buttons generally don't have word wrapping available by design. So increasing a label by using a larger text (not mentioning longer translations, German is bad in that regard ) may make the button label being cut off. Just as one example on how complex this is.
I guess I should start by using this setting in my apps and try to rework them at least step by step.

@gpatel-fr Sure, that's why I said its a personal thing. I am well aware that some people really need larger text. We had other users asking for that feature before. I gladly can still do without. But it doesn't change the situation, that we wish do help them, but haven't got the menpower to do so.

Although signal app might be different being a desktop app, if that allows scaling. So it could be done per app.

I actually compared the text size of teleports with signal app right now. Text in Signal app is a bit smaller than in teleports. This is on OP5T with default scaling at 21.

@mango readability is for sure a very personal thing and depending on your eyesight. I am using UT for ten years now and never saw the need to touch scaling, although I am wearing glasses.

The thing is, as always someone(tm) needs to do the work to allow UT to adjust text size. There needs to be made a setting, all app codes need to be adapted to use that setting. Larger text sizes will break lots of layouts in apps. App and system UI need to be changed to cover for that. This is a HUGE task. We are a small team of mostly volunteers (often non professionals like me) doing the coding in our free time. We don't have a multimillion budget with lots of professional developers.

There have been talks about text size adjustment years ago. And we do understand the need for it. But we simply haven't got the means to do it. So we provide UT for those who can use it, maybe with UT Tweak Tool overall scaling adjusting a bit. But unless you provide code or donate a significant sum of money, sadly I don't think this will change anytime soon.

@Caedem likely not how it works. The 3.5.1 was the last xenial release. Those 9k focal devices, are those who moved from xenial to focal. So there would be a bit less than 4k xenial left with numbers shrinking.

And we need to drop them for security reasons at some point. Or can you justify providing a unmaintained insecure system? Also some older devices will simply die due to hardware breaking.

@pparent No, it doesn't use a popup. After clicking that field another page does open. I do agree, I too don't see why this should fail. Its not a special function.

It might have been simply bad luck or rather bad timing. Maybe the requests had not been synced to this client but my laptop already had them.

But I decided to ask anyway, just in case you might have had an idea. So I guess lets not worry about this.

@pparent When you send someone a group link to invite them, depending on the settings, they need to be validated by a group admin before they can join.

When you tap on the group name to open the details page and scroll to the bottom, there are invites and join requests listed. But I got a zero there, although I had 2 pending invites. Also nothing was listed on the page that opens after clicking that entry.
Just a minute later I checked at signal desktop and there I had a number 2 displayed. After clicking I saw the two requests and could process them.
Of course it could have been just bad timing and lack of syncing.

Is it my bad math, or should +131 -1 = +130, not +129 in the very first paragraph?

Can it be, that admin validation requests of people who want to join via a group link, are not displayed in the app? I didn't saw them, but did see them in Signal desktop on my laptop. Both linked, not primary devices.

@MarcelloTogg Das müsste die entsprechende .zip mit OOS sein. Aber das hatte bei mir irgendwie nie so recht geklappt. Das habe ich mehr dazugeschrieben, weil das auf Hilfeseiten stand und zumindest theoretisch klappen sollte.

@viko As has been said, dtbo.img is generally not needed. If the port doesn't boot, the issue is more like due to other reasons. Feel free to check the porting docs I linked you in Telegram.

@Sander replying from within the app. Thank you very much for adding this great feature.

@Moem time does solve some issues. There actually is a port for OP8 in the works by Scott Howards, he posted some photos on TG. And there is a port for OP8T being done by @aribk and me helping with testing on that. They may end up in the installer and on devices page at some point next year I hope.

@matejrokos I am almost sure its impossible to get any idea or estimate. Volunteers don't do time tracking. Looking at an MR doesn't answer the question if a professional did that in half an hour or a hobby coder in three days.

The foundation numbers may give you an idea about cost for infrastructure. But only partially as well, since we use for instance free hosted weblate or contributors use their own free gitlab CI minutes, so they don't count on the foundation servers.

Volunteers also don't have funding. If they are lucky they get a "thanks" or some smaller donations. But that is not tracked at all.

@matejrokos Please don't expect the foundations money to reflect development cost for Ubuntu Touch. Most development work is done by volunteers who don't get payed.

Und ja: Es gibt einen Port für das OP8T von Ari (@aribk). Er arbeitet gerade daran den soweit fertig zu machen, dass er im Installer und auf der Geräteseite hinzugefügt werden kann. Ich helfe da mit Tests und kleineren Dingen. Läuft schon ganz gut...

Und Scott Howards hat in der englischen Telegramgruppe einen Screenshot von einem OP8 Port geteilt. Aber zu diesem Port habe ich keine weiteren Informationen, außer eben, dass es ihn gibt.

@rocket2nfinity There is a port for OP8T by Ari (@arbk) where I am helping with testing and smaller things. He is currently trying to get things ready to make it available in installer and on devices page. Not sure about status, but should hopefully be available soon.

And there is also a port for OP8 by Scott Howards who shared a screenshot in main group on TG. I have no information about that at all except of this info.

In case you stumble upon this post here first, there is also an English version available at: https://forums.ubports.com/post/91516.