Guido Günther @agx@librem.one

Biggest downside of running #phosh on my phone and laptop: you sometimes try to swipe away notifications on the laptop although it's not a touchscreen 😜 - just happened again .

@okennedy yeah, as @devrtz says: they were around all along and can be enabled via https://gitlab.gnome.org/World/Phosh/phosh/-/wikis/Configuration#under-smpuriphosh - it'd wait for 0.29.0 though as the lack of an animation could make the switching a bit surprising

@eliasr It was uploaded to octarine for early testing at release day (https://lists.community.puri.sm/pipermail/librem-5-announce/2023-June/000015.html) . The PureOS archive restructure makes tickling down to Byzantium a bit slower.

The transition between the normal and HC theme is now supported by an animation making it less surprising (video is at 2 x speed):

3️⃣ /3️⃣

@devrtz added a sensor panel to mobile-settings that allows you to enable automatic HC and tweak the threshold at which ambient light intensity it kicks in:

2️⃣ /3️⃣

It's summer on the northern hemisphere again 😎 so #phosh's automatic high contrast mode got two updates that are already merged and hence will very likely be in 0.29.0:

1️⃣ /3️⃣

@manut Maybe the display section in phoc.ini didn't match? Try `wlr-randr` in a terminal. This is how the output looks at scale 0.5:

@mobian 📱 Congratulations! 🤩 Very happy to see #phosh shipped as default in a stable Mobian release.

@dos Here's he link to the announcement from the PureOS team: https://lists.puri.sm/pipermail/pureos-project/2023-June/000349.html which also has information for those still using #PureOS amber

@sashapgt@mastodon.in.th Nice! https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1158 will help the notch (https://social.librem.one/@agx/110497074841991096) if the cutout information is in gmobile (see e.g. https://gitlab.gnome.org/guidog/gmobile/-/merge_requests/13)

@craftyguy @joao Interesting. That's basically what happens with this MR atm.

@joao optional features (battery percentage, date, ...) are ignored for the calculation - there's not enough space (there isn't even enough space without a notch). There's also the language indicatore for example and the two kill switches.

Landscape: we don't clamp the space on purpose yet. That's a job for the compositor and we want some wayland protocol for that so it's a different topic.

And this is how it looks on a device with notch. Also enabled PHOC_DEBUG=cutouts so phoc renders the bounding box of these.

Finally got to look at this again and instead of just pushing down #phosh's top panel we now place the clock to the left or right based on the available space. The logic is still pretty simple but it covers the cases where we have data for in #gmobile. Will try to land this in 0.29.0.