Closed syrjala closed 3 years ago
I'm not entirely sure how to test this. It definitely builds and runs with --enable-udev
, and my audio works just as well as before, but apart from that I don't know how to tell the difference between master
and pull/33
@vkareh
systemctl --user mask pulseaudio.service pulseaudio.socket
This will disable pulseaudio in user session, than restart your box.
Back in session mate-volume-control
use alsa
and you should see your audio hardware in device tab, if alsa-udev audio-detection from libmatemixer is working.
Don't forget to enable pulseaudio after testing.
systemctl --user unmask pulseaudio.service pulseaudio.socket
@vkareh
systemctl --user mask pulseaudio.service pulseaudio.socket
This will disable pulseaudio in user session, than restart your box. Back in sessionmate-volume-control
usealsa
and you should see your audio hardware in device tab, if alsa-udev audio-detection from libmatemixer is working. Don't forget to enable pulseaudio after testing.systemctl --user unmask pulseaudio.service pulseaudio.socket
I would say the main thing to test would be audio device hotplug. Eg. if you plug in usb headphones/etc. they should get detected immediately.
I would say the main thing to test would be audio device hotplug. Eg. if you plug in usb headphones/etc. they should get detected immediately.
This works well with my usb headset.
Instead of polling for new devices once per second ask udev to send us events. Avoids waking up the CPU all the time and wasting power.
We keep the timeout source as a fallback when udev support is not enabled, or the udev setup fails for whatever reason.
The logic for udev_event_ok() was snooped from pulseaudio.