- 16 Aug, 2022 5 commits
-
-
This message would print for all transports while not even conveying the profile of the transport, and might be printed for non-`HFP_HF` profiles which is the only transport-profile we're interested in. Part-of: <!740>
-
When `indicator` is initialized to `1`: - it always succeeds the `indicator == CIND_CALL_INDICATOR` check; - hence always calls `continue`; - hence never reaches the end of the `while` loop where `indicator++` is called; - hence `indicator` never contains any other value than `1` meaning `cind_enabled_indicators` is ever updated. Part-of: <!740>
-
This reverts commit b05e34e0. Now that backend-native uses a different way to get to its own `native_backend` instance - without going through `pa_bluetooth_discovery` - this patch can be reverted again, as nothing outside bluez5-util is supposed to know the internals of this struct. That's what the many functions are for which all take pointers to this (at that point) opaque struct instead. Part-of: <!740>
-
This removes the inverse/recursive dependency of backend-native on the `pa_bluetooth_discovery` struct, which is supposed to be opaque outside of `bluez5-util` in favour of the many accessor functions defined in `bluez5-util.h`. Part-of: <!740>
-
Replace tabs with spaces, remove trailing whitespace, remove bracing around single-line `if` blocks. Part-of: <!740>
-
- 15 Aug, 2022 2 commits
-
-
Part-of: <!654>
-
Fix the following build failure without C++: ../output-1/build/pulseaudio-16.1/meson.build:1:0: ERROR: Unknown compiler(s): [['/home/autobuild/autobuild/instance-1/output-1/per-package/pulseaudio/host/bin/powerpc64-buildroot-linux-gnu-g++']] The following exception(s) were encountered: Running "/home/autobuild/autobuild/instance-1/output-1/per-package/pulseaudio/host/bin/powerpc64-buildroot-linux-gnu-g++ --version" gave "[Errno 2] No such file or directory: '/home/autobuild/autobuild/instance-1/output-1/per-package/pulseaudio/host/bin/powerpc64-buildroot-linux-gnu-g++'" Fixes: - http://autobuild.buildroot.org/results/6526a21bd4da3b8458188f27c1ec04c381e4b673 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Part-of: <!737>
-
- 01 Aug, 2022 7 commits
-
-
Hook up the UPower backend to backend-native to report the host battery level to the HF. Part-of: <!631>
-
UPower provides information about the power supply and battery level of the host. Add a backend to retrieve the host battery level. Part-of: <!631>
-
AT+BIA is used to enable/disable CIND indicators by Bluetooth HFP spec. By default, all indicators are enabled on connection. AT+BIA will configure which indicators should be disabled then, the disabled indicators may be enabled later on again with AT+BIA. When the connection is lost and recovered, all indicators are enabled again. The HF will reconfigure the indicators again with an AT+BIA command. Part-of: <!631>
-
Part-of: <!631>
-
Signed-off-by:
Rosen Penev <rosenp@gmail.com> Part-of: <!739>
-
Added to shell-completion of zsh as there is no completion for the subcommand get-*. Part-of: <!735>
-
Added to shell-completion of bash as there is no completion for the subcommand get-*. Part-of: <!735>
-
- 22 Jul, 2022 2 commits
-
-
NorwayFun authored
Currently translated at 43.5% (249 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/ka/ Part-of: <!736>
-
Joachim Philipp authored
Currently translated at 94.9% (543 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/de/ Part-of: <!736>
-
- 21 Jul, 2022 1 commit
-
-
NorwayFun authored
Currently translated at 43.5% (249 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/ka/ Part-of: <!736>
-
- 18 Jul, 2022 13 commits
-
-
김인수 authored
Currently translated at 100.0% (572 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/ko/ Part-of: <!736>
-
NorwayFun authored
Currently translated at 29.8% (171 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/ka/ Part-of: <!736>
-
Gogo Gogsi authored
Currently translated at 100.0% (572 of 572 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/hr/ Part-of: <!736>
-
Part-of: <!733>
-
Part-of: <!733>
-
Part-of: <!733>
-
Part-of: <!733>
-
Part-of: <!733>
-
Equalizer control requires server modules only available when daemon is built. Move qpaeq script to be installed together with daemon. Part-of: <!734>
-
Add libatomic_ops dependencies to libraries/modules that showed a failure on an arch that does not have native atomic operations support. Not all optional dependencies were tested, so it is possible that some optional modules are still missing libatomic_ops dependencies. Signed-off-by:
Nicolas Cavallari <nicolas.cavallari@green-communications.fr> Part-of: <!732>
-
Attempting to use atomics operations on an architecture that does not support them generally results in a link error: ld: /tmp/ccjYcMPP.o: in function `func': testfile.c:(.text+0x1c): undefined reference to `__sync_bool_compare_and_swap_4' The current build system uses cc.compiles() to check if atomic ops are supported, but cc.compiles() does not attempt to link, so the test fails to enable libatomics_opts. Fix this by using cc.links() instead of cc.compiles(). Signed-off-by:
-
The full identifier check must be executed for the new melem creation, otherwise the duplicate control element code check is reached. Example (using the snd-aloop driver): numid=56,iface=PCM,name='PCM Notify',device=1,subdevice=1 numid=62,iface=PCM,name='PCM Notify',device=1,subdevice=2 Signed-off-by:
Jaroslav Kysela <perex@perex.cz> Part-of: <!730>
-
The new helem must be tracked and old helem must be cleared to make the code work properly. Introduce the pointer to helem as the private value for melem and add the necessary code. Also, add a check for the duplicate mixer elements. The duplicate mixer element invokes the abort check in alsa-lib. Print a warning instead and handle the exit gracefully. Fixes: def8eb07 ("alsa-mixer: allow to re-attach the mixer control element") Signed-off-by:
-
- 29 Jun, 2022 1 commit
-
-
Jaroslav Kysela authored
Before: device.intended_roles = " voice" After: device.intended_roles = "voice" Signed-off-by:
-
- 28 Jun, 2022 9 commits
-
-
Alper Nebi Yasak authored
Right now we try to add all UCM devices of a verb to a single profile. But if some devices using different PCMs are configured as conflicting with one another, we will only be able to utilize one of them, chosen seemingly based on the order in the UCM config file. This is not a problem with conflicting devices sharing a PCM, as they are assigned to the same mapping and the ports mechanism only enables one of them to be active at a time. To utilize all devices in a UCM verb even when there are conflicting devices using different PCMs, calculate subsets of devices which can be simultaneously used and create a profile for each such set. Signed-off-by:
Alper Nebi Yasak <alpernebiyasak@gmail.com> Part-of: <!596>
-
Alper Nebi Yasak authored
While switching profiles, it was enough to switch UCM verbs since that disables all enabled UCM devices and every profile had a distinct verb. However, switching to the current verb does not disable any devices. To support multiple profiles for a verb we need to explicitly disable the old profile's devices, since they might be conflicting with the new profile's devices and will prevent them from being enabled. Compare both profiles' mappings, and disable the devices not in the new mappings. Signed-off-by:
-
Alper Nebi Yasak authored
After previous patches, we should be generating no combination ports, so we don't need to store multiple modifiers per mapping. Simplify the code based on this. Signed-off-by:
-
Alper Nebi Yasak authored
After previous patches, we should be generating no combination ports, so we don't need to store multiple devices per mapping. Simplify the code based on this. Signed-off-by:
-
Alper Nebi Yasak authored
After previous patches, we should be generating no combination ports, so we don't need to store multiple devices per port. Simplify the code based on this. Signed-off-by:
-
Alper Nebi Yasak authored
A previous commit makes mapping names depend on the UCM device name. Since UCM device names are unique, this means a mapping will at most have one port and thus no combination ports can be generated. This removes the dead code in the pa_alsa_ucm_add_ports_combination() function, unrolls the remaining code in its helper functions that it used, and renames it to pa_alsa_ucm_add_port() to signal that it no longer generates combinations. Signed-off-by:
-
Alper Nebi Yasak authored
PulseAudio combines UCM devices that have the same PlaybackPCM or CapturePCM value into a single mapping with multiple ports. It also creates ports in the same mapping for each valid combination of those UCM devices. Since mappings are the things we put in profiles, we can put in a profile either all devices of a joint mapping or none of them. This causes some complications with device conflicts. For example, a different UCM device might be marked as conflicting with some (but not all) of the devices in a joint mapping. In this case we can do one of three things: - Include all devices in one profile, and hope the conflicting device isn't chosen as the mapping's active port. We shouldn't do this as it puts conflicting devices in the same profile. - Make one profile with the joint group, and one with the other device. This is somewhat acceptable as we have no conflicts, but we sacrifice some compatible combinations of devices. - Do not group the devices into the same mapping, and make one profile for each compatible combination of devices. This appears to be the best option, one where we can always have the maximum number of working devices. This patch chooses the third option and makes one input and/or output mapping per UCM device, by using UCM device names instead of PCM device strings in the mapping names. Signed-off-by:
-
Alper Nebi Yasak authored
Combination port logic calculates some useful properties for device groups that we could reuse while generating multiple profiles to support conflicting devices. Split them into their own functions. Signed-off-by:
-
Alper Nebi Yasak authored
Right now this check is rejecting devices whose UCM config specifies neither a conflicting device nor a supported device list, and accepting devices which specify both. However, a device without neither list is actually unrestricted, and a device with both lists is a configuration error. Fix the check to accept the former. Furthermore, this is missing another case where an already selected device might have a supported devices list that doesn't have the candidate device. Make this function also check against that, and also make it accept devices already in the set. Signed-off-by:
-
