My #FreeSoftware Activities for April 2025: https://honk.sigxcpu.org/con/Free_Software_Activities_April_2025.html
honk.sigxcpu.org
Mostly #phosh/#LinuxMobile (e.g. alarm-clock, #feedbackd, #Cellbroadcast) related but also some #Debian bits.
to everyone supporting this!
In case you're using a @frameworkcomputer 13 Laptop and want to use the power LED as status LED for #feedbackd (to be notified aboutnotifications in #phosh, etc) you can use this #udev rule:
There's a warning as the LED claims to be multicolor but it's not. That warning will go away with the next #feedbackd release.
Not much news on other mobile platforms but I needed a reliable clock that wakes me up even when the 
is suspended so I added some boottime clock support to #gnomeClocks.
This together with #feedbackd support can be found in https://gitlab.gnome.org/guidog/gnome-clocks and #phosh's nightly packages.
In preparation for the upcoming phosh release we've released new versions of #gmobile 0.2.0 and #feedbackd 0.8.0. Feedbackd is now more flexible regarding haptic feedback for events so if e.g. feedback is too intrusive (or too weak) you can consider submitting adjustment for your device to https://source.puri.sm/Librem5/feedbackd-device-themes/
Ever since adding the `Haptic` API to #feedbackd for games I wanted to make the `VibraPattern` available to feedback themes as well as this allows for more nuanced feedback.
This allows us to e.g. use more subtle feedback for OSK button presses than for 
of incoming SMS.
Opened MRs to make that possible and
while at that I made the maximum strength for all events confiurable too. It's a bit hard to 
in the 
but it's there. Hopefully this makes it into #phosh 0.46:
I always wanted a simple way to put the phone to silent mode when e.g. placing it on the table next to the 
. Since Biemster got NFC to work on the Oneplus 6/6T (https://github.com/biemster/pmos-openbox-conky/blob/main/nxp_nci_i2c.py) we can leverage that and have feedbackd's profile adjusted when certain RFIDs are seen (https://source.puri.sm/Librem5/feedbackd/-/merge_requests/154). For this to land we want to move the NFC support from a python script to s.th. like nfcd (https://github.com/biemster/pmos-openbox-conky/pull/18#issuecomment-2653920089). Help on this would be appreciated.
In preparation for the next #phosh release we've released #feedbackd 0.7.0 
:
This adds a new hint to events so that they can override the sound file used. https://source.puri.sm/Librem5/feedbackd/-/releases/v0.7.0
We had a discussion in matrix (kicked off by @fizzo) if we could make telegram-desktop's notification adhere to #phosh's full/quiet/silent profile. Turns out (https://github.com/telegramdesktop/tdesktop/issues/28895) that the app detects the notifications servers sound capability already so with https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1618 and the corresponding #feedbackd MR this should work.
As I'm not a #telegram user, testing feedback would be welcome.
In preparation for the next #phosh release we've released #feedbackd 0.6.0 :
This adds support for a new haptic API to feedbackd that can be used by e.g. games to trigger vibration patterns or by browsers to implement `navigator.vibrate()`.
Waking my #Librem5 from suspend when a new #matrix message triggers a notification.
Starring:
Thanks to the bits and pieces collected by @isyourbrainFOSS we can now support the alert slider on the #Onplus6/6T to toggle #feedbackd's full/quiet/silent profiles.
Today was "Bundesweiter Warntag" in Germany so a good point in time to test #ModemManager's & #phosh's upcoming #cellbroadcast support 
.
The sounds emitted by #feedbackd are only stubs (and you don' t hear the haptic in the video but I promise it's there 
).
There's three messages because the CBMs are sent out on three different channels.
Thanks @NGIZero for supporting my work on this!
Receiving SMS plays a long tune on my #Librem5. For a few persons I'd like to have this tune played also if they send me a message using #matrix.
A problem is that the #fractal flatpak does not use #feedbackd yet to signal new messages and on #PureOS #Byzantium there's no way to define different sounds for different notification events.
So I started testing a small script to read notifications and trigger feedback for messages coming from an account containing some string:
#!/usr/bin/python3
import gi
import time
gi.require_version('Lfb', '0.0')
from gi.repository import Lfb
from gi.repository import GLib
import dbus
from dbus.mainloop.glib import DBusGMainLoop
def print_notification(bus, message):
keys = ["app_name", "replaces_id", "app_icon", "summary",
"body", "actions", "hints", "expire_timeout"]
args = message.get_args_list()
if len(args) == 8:
notification = dict([(keys[i], args[i]) for i in range(8)])
if "account_i_want_to_be_notified_for_like_it_would_be_sms" in notification["summary"]:
print( notification["summary"], ': ', notification["body"] )
event.trigger_feedback()
Lfb.init('org.sigxcpu.lfbexample')
event = Lfb.Event.new('message-new-sms')
loop = DBusGMainLoop(set_as_default=True)
session_bus = dbus.SessionBus()
session_bus.add_match_string("type='method_call',interface='org.freedesktop.Notifications',member='Notify',eavesdrop=true")
session_bus.add_message_filter(print_notification)
GLib.MainLoop().run()
In preparation for the next #phosh release we've released #feedbackd 0.4.0 :
- Support `hw_pattern` on devices using qcom-lpg. This allows to keep LEDs on in suspend on these
- Support RGB color mixing for multicolor leds
- Allow to use (camera) flash LEDs as notificaton LED
- Immediately end "too noisy" feedbacks when switching profile levels
- Internal cleanups and restructuring to cater for different LED types.
https://source.puri.sm/Librem5/feedbackd/-/releases/v0.4.0
This 
has some demos: https://fosstodon.org/@phosh/112625626399977365
Finally we now end the emitted feedback when switching the profile level. We can use this in #phosh to put the device into silent mode when pressing Vol- on
incoming calls when the phone is locked (turn on audio for this one):
…and it helps on devices that don't have a status LED at all (in these case we can even tweak the device specific theme for that (e.g. to reduce the flash brightness):
In some situations using the camera flash instead of the status LED can be useful (e.g. if you prefer to put your phone with the display side down on the table). A new setting allows to prefer the flash led (giving us room to expand this to e.g. basing this on other factors like device orientation later on):
Initially #feedbackd supported a set of color names (that matched the LED color) as multicolor LED support was still in the makings in the kernel. With the next release you can use arbitrary RGB colors (#RRGGBB). On single color
leds we still fall back to that color.
@agx worked on making #feedbackd a bit more useful and convenient. Some of this landed already and is targeting the next #phosh release
while others might take a bit longer (as they e.g. depend on a calls bug fix release). A short
#feedbackd uses the 's notification 
on events like missed phone calls, notifications, etc to alert the user.
Thanks to @dylanvanassche this now supports hw-pattern LEDs (currently for devices using the qcom-lpg LED driver found in various).
This doesn't only free the CPU from processing the blink patterns but more importantly allows us to keep the LEDs blinking in suspend so we have another missing piece in place to make suspend work nicely.