@pparent my description was maybe not clear enough. The power button itself works. It brings up the power menu, but pressing the buttons failed. But I can't reproduce it right now (after a reboot). So who knows...

@undrwater I think it may not be a general aversion to guestures, but UT already has some implemented. So adding more without breaking something and doing it in a nice way isn't easy.

@pparent thanks a lot for the quick response. Just some feedback in case others try that:

yes, the app now opens, but...

• I can't close it, when swiping into the drawer, it becomes a transparent window which I can't swipe to close
• I couldn't reboot with the power button since that was somehow blocked

I hope that makes some sense to you.

@Ida_ ah, ok. Not iedal, but sometjing. I get less than a second. I am not that quick in reading.

@pparent please don't get me wrong. I know that 2.x daily is bleeding edge, so I don't expect you to fix that imediately. Just wanted to share my experience.
Interesting that @ida_ gets it working eventually. Maybe I would need to try more often.

@CiberSheep to be honest, I disagree here. In my opinion we rather should update our HIG design to cover/allow for other app navigation methods.
For instance OP8T (and another device which I don't remember) has the camera exactly where the back button sits. And this back button IS hard to reach with phones getting larger. This is a problem coming up again and again for a reason.
Yes, there is no universal back, but there is in-app back.

@Moem I just tried it on 24.04-2.x daily. The app opens, loads messages, briefly shows the chat list and then crashs. On the second start if hangs at the splash screen. So no, broken on 2.x.

@richdb Isn't beeper technically working like a bridge (collection of bridges)? There are also other signal bridges out there, or one can self host one.

@messayisto I just checked on my signal bridge room. That has encryption enabled. So in theory it should work this way. But of course no idea if it would work when setting it up new again. Sometimes old tjings work and new ones break.

@messayisto Matrix bridge signal is linked as a secondary device to your signal installation. I never did that since using the bridge, but I can guess, that when changing your primary installation for Signal, you may need to connect all secomdary linked devices again. Would kimd of make sense.

Regarding "login" and no answer, I don't have much advice, but only know that matrix bridges can hang. If there is no message/reply at all, best try again later or zry to find out if your bridge works. I had it before, that the bridge was down or flooded or whatever and the bridge maintainer had to fix something. So have some (a lot) of patience might be needed.

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