Modules responsible for storing device settings
In a default pulseaudio setup the following modules are loaded to restore device settings, and volume settings changed by the user at runtime:
restores the volume of an audio device to previous values.
restores audio card settings (for a headset this will be A2DP or HSP/HFP mode).
Both modules (amongst many others) will be loaded from settings in
/etc/pulse/default.pa. If we had made a custom
~/.pulse/ these custom setting will override the defaults in
Make sure that both module are loaded when starting pulseaudio. To see which modules are in operation we may issue:
In case they are misssing we need to add them to our
default.pa with the following lines:
Values for a given device will then be stored in a database located in
~/.pulse/, depending on release version.
Remove the pulseaudio database after settings were bad
In case of erroneous setting we can remove all entries to this database by renaming or deleting these directories. Changes will only take effect after restarting pulsaudio (the configuration directories will then be re-created with default values) with:
Then any audio application will use the custom user settings after switching output sinks. To automatically switch between internal audio and a Bluetooth audio device we can add the following module to our
default.pa or as command for
pactl on the command line:
Applications can override this
In case an application had defined it's own audio setting (this can also be done while playing audio with pavucontrol ) these settings will override the default settings we had made.
In case our volume or card settings are not restored as expected we therefore need to remoe those application based settings. We can do so by changing the output device properties in pavucontrol, or again by removing settings which should be stored in
~./.config/pulse with deleting these directories.
If all this does not help we may be faced with an application storing defaults in a different directory, or not respecting the pulseaudio settings (which then could both be considered as a bug).