One thing that bugged me is that we had no way in #phosh to present only the available OSK layouts to the user to pick from. This led to confusion as users configured a layout which then would not be available later on. phosh-osk-stub can now provide that information to mobile settings (and it will be simple to add support for e.g. squeekboard if it dumps out the relevant information).
Thanks to #libadwaita and #GTK4's list models such things are fun to add.
Evangelos talking in the FOSS on Mobile Devroom at #FrOSCon 2024 about debugging the #phosh / #gnome stack. #LinuxMobile #ShotOnLibrem5
@arunmani and myself worked a bit on making Wi-Fi networks easier to select in #phosh's quick setting status page by giving the Wi-Fi list more vertical space and making each list box row a bit wider thus making it easier to select via touch (the same applies to other status pages like Bluetooth device selection):
Can't join #GUADEC (https://events.gnome.org/event/209/) this year but at least I can watch the live stream on a 📱 running a #gtk based shell (#phosh) and lots of #gnome components with a video player using GTK and #gstreamer (#livi). Life could be worse.
While @suraj_sloth is working on the #UnifiedPush connector side in #Chatty I got a chance to add the code for registering/unregistering #Matrix push gateways in #libcmatrix and Chatty (with this I can readily round trip messages up to the UP distributor):
So far you had to pull out #phosh's top and bottom bar quiet a bit to make it unfold. That's kind of o.k. on 📱 like the #Librem5 or #PinePhone but can be cumbersome on larger phones like the #OnePlus6T or tablets like the #Librem11. I've put out an MR for #phoc which adds a fling #gesture so you can also fold/unfold with a fast swipe. Here's a short video demoing this for different screen sizes:
Was able to grab the #nlalert2024 #cellbroadcast message with our WIP #ModemManager patches. #phosh will use the same interface.
I remember how nervous I was when (in early 2020) I went to the post office with my #Librem5 📱 to drop off a 📦 and present the barcode on the phone. (Having previously scp'ed the pdf to the phone to show it in evince).
Would the 🔋 last? Would it overheat? Would the display stack hold? It worked.
Nowadays I don't spend a thought: Fill in the data on my laptop, save the pdf, have it synced automatically via #syncthing to #phosh's ticket-box folder and show it at the counter. ✅
Laptop died yesterday but thanks to the #Librem5, the Baseus Dock, an HDMI Screen, a USB keyboard and #Phosh's docked mode I have access to most of the things via my phone.
#nitrokey helps a lot as that means I have my ssh keys available by just plugging it in.
Took me about 15min to notice that I didn't even plug a mouse in.
Forgot to add: toggling always-on-top will also get a visual indication in an upcoming #phoc release (likely 0.39.0).
While we try to find a suitable place for the clock in phosh's top bar when notches are present (since 0.29.0) we didn't take rounded corners into account as most of the time the left and right padding would be enough.
With more devices like the #fairphone5 and #xiaomi daisy showing up as being used with #phosh we need to care about that too:
With a bit of help from #phoc the next phosh-osk-stub release can (optionally) hide when a keyboard gets attached.
I kept unlocking the 📱 a lot to check a cars charging status. Using #phosh's launcher-box lockscreen-plugin and the LauncherEntry DBus protocol we can simplify that and have the information easily accessible:
I finally resumed work on the MR that allows for a non solid background in #phosh's overview. There still some lose ends, but it's progressing:
I've released version 0.0.6 of livi - the little video player for mobile: https://gitlab.gnome.org/guidog/livi/-/releases/v0.0.6
While this also adds a bunch of new features like language and subtitle selection it mostly moved things closer to the designs. We have a wide mode for docked/desktop mode now and autohiding of panels, etc.
