Skip to content

Conversation

@rbujala-quic
Copy link

The BlueZ monitors are integrated with logind to
ensure that only one user at a time can use the
Bluetooth audio devices.on QLI devices, there is
no user login sessions enabled. so disable this
feature will allow bluez plugin to launch without
looking for logind session.

Add bluetooth configuration file in wireplumber
delta conf folder for user preferred configuration.

SYSTEMD_SERVICE:${PN} = "wireplumber.service"
SYSTEMD_AUTO_ENABLE:${PN} = "enable"

SRC_URI:append:qcom = " file://0001-Enable-bluez-plugin.patch \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep the same flow of the recipe in the bbappend: SRC_URI right below FILESEXTRAPATHS, do_install:append above SYSTEMD_*.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

update as per the suggestions and removed existing flag from the change.

hardware.audio = required
hardware.bluetooth = required
hardware.video-capture = required
+ monitor.bluez.seat-monitoring = disabled
Copy link

@anujm1 anujm1 Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems this flag is already available as part of mixin from wireplumber 0.5.6 and it did not require further.
thanks

Add bluetooth configuration file in wireplumber
delta conf folder for user preferred bluez configuration.

Signed-off-by: Raghavender Reddy Bujala <[email protected]>
do_install:append:qcom () {
install -v -m 0644 \
${S}/src/config/wireplumber.conf.d.examples/bluetooth.conf \
${D}${datadir}/wireplumber/wireplumber.conf.d/
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this is already getting installed in /usr/share/doc/wireplumber/examples and the contents are commented out. So, what does this achieve?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bluetooth.conf file is not seen on target and this we have added for user to choose bluetooth configurations for connection and to set sampling rate etc.,

user has to uncomment and use the preferred settings.
one example: this is required for switch between native and ofono for hfp client usecase
bluez5.hfphsp-backend = "native"

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This goes in wireplumber-doc which I think is correct since this is essentially an example and not doing anything.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is required, without this we can't test ofono usecase and hfp client will be considered as depored.
and this needs to be in /usr/share/wireplumber/wireplumber.conf.d/ folder to pick the configuration

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't look like there is anything defined in that file, most of the lines are commented out. Please either fix it via the patch or provide an actual config file in the repo and then install it to the target. In the latter case, I'd recomment installing it via a separate package instead of hijacking the wireplumber recipe.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to enable a runtime-based configuration, then have the fragment you want in a separated package, which the user can then install based on the desired default behavior.

@lumag lumag closed this Dec 2, 2025
@lumag lumag reopened this Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants