feedback-manager: Only act on add
We would otherwise ignore the action when no vibra device was yet found. Make sure we release the old device when updating.
View Articlefeedbackd: Add helper to set up permissions for LEDs
This helper knows about the tiggers and necessary permission. It's intended to be run via udev.
View Articlefeedbackd: Support visual feedback via LEDs
Currently all LED feedbacks are infinite we can improve that later on by using the 'repeat' attribute of the LED pattern trigger.
View Articlerumble: Use a default pause
Without that multiple counts sound odd so let's have good defaults.
View Articlefeedback-manager: Prepare for per event hints
Move feedback profile level into a separate function for that.
View Articlefeedback-manager: Add hint to select feedback profile per event
This e.g. allows events that are meant for haptic only to avoid emitting a sound by omitting the 'full' level and using "quiet" instead. Closes: #7
View Articlefbd-dev-leds: store LED color when parsing devices
Failing to do so will always select the first recognized LED (the blue one for the PinePhone).
View Articlefbd-dev-sound: Be less verbose on missing sound files
This is quite common so don't fill the logs at normal debug levels but be more specific about what is missing.
View Articlefbd-feedback-base: Add fbd_feedback_is_available ()
This allows to check if a feedback type is available at all.
View Articlefbd-feedback-manager: Check if feedback is usable
If we don't find any usable feedbacks for an event return FBD_EVENT_END_REASON_NOT_FOUND.
View Articlefbd-feedback-led: Implement is_available ()
This avoids criticals when there's no Leds available.
View Articlefeedback-vibra-rumble: Implement is_available
This avoids criticals when there's no rumble vibra available.
View Article
