Sebastian Krzyszkowiak @dos@librem.one

@ceelight @flow3rbadge Glad it does! Enjoy, and don't forget to upgrade the firmware 😊 (1.3 should be out soon-ish now)

@scottjenson @jeremy_data @dcz You may also be interested in text-input Wayland protocol that lets the OSK and apps communicate with each other: https://wayland.app/protocols/text-input-unstable-v3

There have been lengthy discussions taking place on what is needed for the next versions of the protocol: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/39

@scottjenson @jeremy_data @dcz Surprisingly, not that much actually - some things had to be fixed as they were poorly tested or bit-rotten, but as far as I'm aware most of the underlying stuff in GTK dates back to GTK3's initial push for touchscreen support around the time when laptops with touchscreens started appearing on the market.

I guess libadwaita may be a place for some of this stuff too.

@scottjenson @jeremy_data Fixing some of these stuff will be quite an undertaking and most of them are actually handled by toolkits rather than OSK, but I'm pretty sure that at least @dcz will be eager to discuss 😁

@scottjenson @jeremy_data Hello from my Librem 5 running Debian-based PureOS 👋😋

@elgosz @scottjenson @jeremy_data Pine64 has no software developers. Purism does, and then there are contributors from various communities.

These are the keyboards commonly used on mobile phones:

- https://gitlab.gnome.org/World/Phosh/squeekboard/
- https://github.com/maliit/keyboard
- https://gitlab.gnome.org/guidog/phosh-osk-stub
- https://git.suckless.org/svkbd/

Phosh & Squeekboard devs can be easily reached via Matrix: https://matrix.to/#/#phosh:talk.puri.sm

@ceelight @flow3rbadge Which red LED? If it's the one on the petal 8 (next to the microphone), then it's most likely the connection between the boards being misaligned. Make sure all the screw holes are perfectly aligned before connecting the boards.

If it's the one next to USB-C, then power cycle it through the power switch (and remember to (dis)assemble it with it set to OFF!). If it still doesn't help, check the display connection.

@hrw @andypiper Yup: https://www.openmoko.org/wiki/USB_Product_IDs / https://github.com/openmoko/openmoko-usb-oui

@devrtz Yeah, and the overhead of shelling out to separate process for each frame is likely not insignificant too 😅

@devrtz ooooh when it comes to videos there's *much* more low hanging fruits to optimize there!

@mykolak Maybe your response got lost in transit? Get in touch with support, your phone is waiting for you: https://puri.sm/posts/we-have-your-phone-ready-to-ship/

That said, you don't need huge powerful but complex tools like #darktable or #rawtherapee to make your photos look better. Imagine a simple to use app that lets you do basic stuff on the phone, like white balance or contrast correction, which could then take its time exporting at full res with all the heavy noise reduction algos without annoying the user while taking photos.

Does that sound like something you'd like to work on? 😁

#mobilelinux #linuxmobile #linuxsmartphones #librem5 #pinephone

For practical reasons, photos that you #ShotOnLibrem5 are processed into JPEGs with lower quality than what the camera can do. There are some (complex) ways in which this processing could be made faster and therefore cram more pixels and algorithms that make things prettier, but meanwhile...

Each photo you take is stored as both raw DNG and processed JPG - so you can go back to raw data and retroactively gain quality. See https://dosowisko.net/l5/photos/ for an example.

(cont.)

#librem5 #mobilelinux

@fell Watch out for its USB port! It likes to go places, and the used ones often already have some history 😅