Some progress to handle notches / cutouts of #linuxmobile phones better in #phosh : I have a small lib that gets panel cutout / notch information as #svg paths and can calculate a bounding box . #phoc can use it to render cutouts for debugging and #phosh can use it for layout (so far only to shift the panel down). (see follow up posts for more pictures).
@agx On my OP6 I currently shift the clock to the right. I'd much prefer a smaller panel with more efficient icons e.g. signal bar with 4G could be combined and location could be on the left to allow wider date or battery percentage which could also be part of the icon. 250% scale is perfect for this phone but messes up the keyboard and lockscreen.
@agx Not as far as I know, using stock pmOS but adjusted things with the Tweaks app provided with the image, that might change the css?
@joshfowler hmm...seems my reply somehow vanished: pmOS tweaks sets CSS which likely causes your problem. Basically if you add additional CSS you got to keep the pieces.
There's some other caveats with fractinal scaling atm but phosh itself should render correctly at scale 2.5 (it does here on current main).
@agx I removed the customisations in ~/.config/gtk-3.0/gtk.css, rebooted, changed the scaling and it still does the same thing to the keyboard.
@joshfowler But lockscreen is fixed?
Your screenshot show's squeekboard so I assume you're hitting https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/338 . I'm using phosh-osk-stub instead as I rely on some of it's features and that ones scales according to the screenshot I posted.
@agx My apologies "messes up the lockscreen" isn't very descriptive so I will attempt to explain better. The scaling on the lockscreen is correct, same as in Phosh, but it groups the numbers together on the numpad input because it is scaled away from the edges of the phone. At 300% scaling I regularly miss a number when unlocking, with 250% it's every time.
Aha, so there is a different keyboard! Do you know of a guide to switch between them?
@joshfowler Ah regarding lock screen, you want to send patches to allow for more spacing between the keys and maybe even scale up a bit.
Regarding switching keyboards:
That depends on your distro. In Debian it's just `update-alternatives`. On pmOS building from source and installing to `/usr/local/` should do the trick. That's at least how I run it there for testing. Note that phosh-osk-stub is experimental so make sure you have ssh access.
@agx Thank you for taking the time to help me out with this BTW.
How did you get OSK to compile? It gives a dependency issue for gnome-desktop-3.0 when I follow the meson build instructions and I can't see anything other than 43 in the repos.
@joshfowler gnome-desktop 43 provides a libgnome-desktop-3 and libgnome-desktop-4. See e.g. how Debian handles it: https://salsa.debian.org/gnome-team/gnome-desktop/-/blob/debian/master/debian/control#L88
@joshfowler This is the list of dependencies I use to build on pmOS/alpine: https://gitlab.gnome.org/guidog/phosh-osk-stub/-/blob/main/.gitlab-ci.yml#L29 , https://gitlab.gnome.org/guidog/phosh-osk-stub/-/jobs/2546824 has a build log that hopefully has all the details.
@agx Excellent, that got everything compiled but I get an error and a critical when I try to replace sqeekboard, pic attached.
@joshfowler Replacing a runing squeekboard doesn't work yet (https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/361) - replacing a running phosh-osk-stub with another phosh-osk-stub does though. To replace (temporarily) replace squeekboard you need to make sure sm.puri.OSK0.desktop invokes phosh-osk-stub, other by editing it, adding one to /usr/local/ or ~/.local/share/applications or (on Debian) by using `update-alternatives`: https://gitlab.gnome.org/guidog/phosh-osk-stub/-/blob/main/doc/phosh-osk-stub.rst