05:16 <yifei1> Wizzup: it's `xrandr --output DSI-1 --primary`

09:19 <Wizzup> yifei1: ok

09:20 <Wizzup> and you run this just before h-d starts?

10:43 <yifei1> Wizzup: yes, although I still don't know why this happens, maemo's codebase is quite complicated and sadly I haven't got much time for it...

11:24 <Wizzup> yifei1: the problem is not in maemo, its in X / kernel / dts

11:24 <Wizzup> as I understand it

16:10 <nerdcore> is it possible to increase all the fonts or set other visual accessibility settings throughout the interface?

16:11 <nerdcore> I poked around in Fonts and Themes and Profiles and Display inside the Settings area but didn't find any global font or accessibility options

16:24 <Wizzup> I don't think so, is this for a high res display?

16:24 <Wizzup> once we finish a the gtk3 theme port then we could do this perhaps

16:29 <Wizzup> sicelo: can we get an icon for OTP?

16:35 <Wizzup> we could call it 'Maemo Authenticator' :p

16:35 <Wizzup> or just 'Authenticator'

16:36 <Wizzup> we could also have the user guide actually launch or documentation / user guide

16:42 <nerdcore> it's on a PinePhone which is I guess 1920x1080. it's far too small for me to read without visual aides (magnifier)

16:43 <nerdcore> I was able to bump up the font size in the "X Terminal" onlyu

16:46 <nerdcore> so I don't think it is a particularly high resolution display device, I just have a visual disability is all.

16:51 <gnarface> uh, pinephone isn't 1920x1080 i don't think... it's something like 768x1100 or something weird like that

16:51 <gnarface> unless you're talking about connecting it to an external display...

16:52 <gnarface> the problem with fonts in linux in general is there isn't just one place to set a default size. usually each toolkit (gtk/gtk2/gtk3/gtk4/qt/efl, etc) has their own config for it and some programs have one just for themselves

16:52 <gnarface> (and then to make things even more confusing, some desktop environments tack on their own font scaling on top of that)

16:53 <gnarface> nerdcore: pinephone or pinephone pro? my regular pinephone is reporting 720x1440 as the display res

16:55 <gnarface> hmm, but maybe that's with scaling... xrandr is actually reporting 360x720 but that doesn't sound right

16:55 <gnarface> hmm, no it must be 360x720 and phosh is scaling it? not sure

16:55 <gnarface> it's definitely not 1920x1080 though

16:56 <gnarface> (and having the DPI wrong can also be a complication for some toolkits to render font sizes accurately)

17:02 <nerdcore> yes I realize each toolkit manages fonts differently, but in KDE (QT) there is a global "Scale the entire UI %" setting, and in Gnome (phosh, etc) there is a "Large Fonts" setting which bumps every font rendered by gts3

17:02 <nerdcore> gtk3

17:04 <nerdcore> and as an end user I would expect any modern GUI to enable some of these basic accessibility features to support people living with disabilities

17:04 <nerdcore> it is in fact a PinePhone original and I see that xrandr reports 720x1440

17:09 <Wizzup> yes, maemo being on gtk2 suffers from this issue

17:09 <nerdcore> in each of gnome, kde, lxde, phosh I've been able to set some global settings which affect their areas of responsibility, such as increaing the taskbar fonts where running applications and the clock are displayed, or their own Settings applications so I can read what the settings are. I realize this does not affect 100% of X-based applications (such as xterm for example)

17:09 <Wizzup> we are planning to move it to gtk3

17:10 <Wizzup> you could alternatively maybe just scale the whole X display

17:10 <Wizzup> I suppose it might work ok with qt5 applications on maemo

17:10 <nerdcore> how would I scale the whole X display Wizzup ?

17:10 <nerdcore> that does sound good to me

17:10 <nerdcore> I desire a "make everything bigger" option :)

17:11 <Wizzup> something like this: xrandr --output displaynamehere --scale 2.0x2.0

17:12 <Wizzup> but you might need to restart hildon-desktop or some other programs for it to pick up on these changes

17:12 <Wizzup> via xorg.conf you could make it more permanent I suppose

17:12 <nerdcore> okay I can try that (might start with 1.2 or 1.5x first heh). If I like it, how would I set it for startup?

17:12 <nerdcore> ah ok ty

17:13 <Wizzup> https://wiki.archlinux.org/title/HiDPI

17:13 <Wizzup> let us know how it goes

17:17 <nerdcore> I erroneously assumed the default would be 1.0x1.0 so I tried "1.2x1.2" and everything got smaller heh

17:17 <nerdcore> rebooting the device now

17:20 <nerdcore> Wizzup: the xrandr command you provided does not seem to have the desired effect. It shrinks everything instead of making it larger, and messes up the onscreen keyboard so it no longer displays properly

17:21 <nerdcore> is this --scale option inverted somehow? maybe 0.8x0.8 makes things bigger? seems weird but I will try it

17:22 <Wizzup> yeah try it :)

17:23 <nerdcore> the OSK certainly did not seem to work properly though :(

17:25 <Wizzup> this might also need to be restarted, it might work fine if the scale is set on boot

17:25 <Wizzup> but you're on unchartered grounds :)

17:25 <nerdcore> okay that seems to be the trick. "--scale 0.8x0.8" made things BIGGER (weird)

17:25 <nerdcore> now I cannot access all the apps in the Launcher screen because they are rendered off the side. How do I restart the launcher?

17:26 <nerdcore> haha the lockscreen came on and I cannot swipe to unlock now

17:27 <Wizzup> best to get ssh access first

17:27 <nerdcore> I will try to set it in xorg.conf and restart at least to report on the results.

17:28 <Wizzup> then you can kill hildon-home and hildon-desktop

17:28 <Wizzup> (they get restarted)

17:35 <nerdcore> seems to be working now Wizzup tyvm!

17:35 <nerdcore> not sure exactly where xorg.conf resides or should be edited though. /etc/X11/xorg.conf.d is empty

17:36 <nerdcore> lockscreen and launcher render as expected with larger scaling after restarting hildon-home and hildon-desktop

17:36 <Wizzup> nerdcore: would you share a screenshot with us?

17:37 <Wizzup> nerdcore: you can also make a xsession with this xrandr command

17:39 <nerdcore> that latter part I think I can manage... right now the wifi is switched off on the dip switches of my pinephone and my SIM card is in another phone, so no easy way right now to get files in/out

17:39 <nerdcore> how do I make screenshots in ML?

17:42 <Wizzup> scrot

17:42 <Wizzup> or ctrl+shift+p or something

17:42 <Wizzup> (if you have a keyboard)

17:43 <nerdcore> just the OSK for the time being, but I can run `sleep 15 ; scrot` in a terminal easily enough

17:43 <Wizzup> yeah

17:44 <nerdcore> I have found in my first hour running ML that the terminal application is a bit difficult to manage command history, but my extensive knowledge of Emacs key bindings served me well enough lol

17:45 <nerdcore> ^P^B^B^B^B^B^B^B^D^D etc heh

17:46 <sicelo> Wizzup: please open an issue :-p

17:47 <nerdcore> can I make the OSK stay up while typing? I'm trying to write a shell script but every time I press Enter the OSK goes away

17:48 <Wizzup> sicelo: https://github.com/maemo-leste/bugtracker/issues/736

17:48 <Wizzup> nerdcore: yeah, OSK from maemo times was kind of made assuming you also had a keyboard

17:48 <Wizzup> imo one of the main maemo (leste) current shortcomings are lack of virtual keyboard in qt applications and the osk/vk not being great for terminals at all

17:49 <nerdcore> is that a "no"? ;)

17:50 <nerdcore> I have a USB-C hub here somewhere. It worked great in postmarketos on the PinePhone but for some odd reason never works on my PineTab2 with Arch... I'll try it in ML in a bit.

17:50 <Wizzup> nerdcore: yes, it won't stay up after you hit enter

17:50 <Wizzup> usb otg/c should work fine

17:51 <Wizzup> what I am trying to say is that maemo leste inherits some good things and some not so good things (virtual keyboard)

17:51 <Wizzup> and some of these we need to tackle/fix

17:51 <Wizzup> (still)

17:54 <nerdcore> idk wtf... I plugged in my USB-C hub and standard USB keyboard and I swear it worked for like 10 seconds until I touched the screen and initiated the OSK, and now the physical keyboard no longer works

17:55 <nerdcore> I guess I can take the SD card out, put it in my PC, write my shell script, and boot back up again :/

17:55 <nerdcore> maybe later.

18:00 <Wizzup> strange

21:52 <uvos> Wizzup: latest 6.6 stable -> cpufreq not working also lots of other stuff would have to be rebased

21:53 <uvos> Wizzup: curent linux master, no patches-> same

22:18 <Wizzup> uvos: thanks for checking

22:18 <Wizzup> can you push this somewhere

22:18 <Wizzup> I'd like to check

23:02 <Wizzup> uvos: what do you mean with lots of other stuff would have to be rebased?

23:46 <Wizzup> uvos: for 6.6+ you mean?