From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b8d3e4: shared/hfp: Add Operator name support
Date: Wed, 17 Sep 2025 06:29:16 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/4d7d25-c6dcf6@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b8d3e4c510b81e152f70618f17698329ebe48335
https://github.com/bluez/bluez/commit/b8d3e4c510b81e152f70618f17698329ebe48335
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-15 (Mon, 15 Sep 2025)
Changed paths:
M src/shared/hfp.c
M src/shared/hfp.h
M unit/test-hfp.c
Log Message:
-----------
shared/hfp: Add Operator name support
Send AT+COPS=3,0 at the end of the SLC creation to set the format of
the operator selection to long alphanumeric, then query the currently
selected operator name from the AG.
Register +COPS handler to call the update_operator callback on event.
Commit: fb32f3a27fbddabfa678c19f82297d7e4509c73c
https://github.com/bluez/bluez/commit/fb32f3a27fbddabfa678c19f82297d7e4509c73c
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-15 (Mon, 15 Sep 2025)
Changed paths:
M unit/test-hfp.c
Log Message:
-----------
unit/test-hfp: Add Operator name test for HF
This add the following test:
- HFP/HF/PSI/BV-04-C
Verify that the HF can query the currently selected operator name.
Improve MINIMAL_SLC_SESSION macro to be able to set the service, call,
callsetup and callheld indicators at connection time.
Commit: 889139e0a1af317d0964b8ef989e974709ccff0f
https://github.com/bluez/bluez/commit/889139e0a1af317d0964b8ef989e974709ccff0f
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-15 (Mon, 15 Sep 2025)
Changed paths:
M src/shared/hfp.c
M src/shared/hfp.h
M unit/test-hfp.c
Log Message:
-----------
shared/hfp: Add Call Line Identification support
Send AT+CLIP=1 at the end of the SLC creation to enable CLIP event.
Register +CLIP handler to call the update_call_line_id callback on event.
During incoming call notifications, i.e. after +CIEV:<callsetup>,1
event which creates a new call object, the reception of +CLIP event
will update the line_id and type of the call object.
Commit: 430b8b1b024b4f452aa1f641137c9b132c812435
https://github.com/bluez/bluez/commit/430b8b1b024b4f452aa1f641137c9b132c812435
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-15 (Mon, 15 Sep 2025)
Changed paths:
M unit/test-hfp.c
Log Message:
-----------
unit/test-hfp: Add Call Line Identification test for HF
This add the following test:
- HFP/HF/CLI/BV-01-C
Verify that the HF receives the caller ID.
Commit: c6dcf6b714501768ab7ea293e75d945be0eec188
https://github.com/bluez/bluez/commit/c6dcf6b714501768ab7ea293e75d945be0eec188
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-09-17 (Wed, 17 Sep 2025)
Changed paths:
M configure.ac
M profiles/audio/transport.c
Log Message:
-----------
transport: Fix build with VCP support disabled
$ $ ./bootstrap-configure --enable-a2dp --enable-avrcp --enable-experimental --enable-asha --disable-vcp && make
[...]
/usr/bin/ld: profiles/audio/bluetoothd-transport.o: in function `transport_bap_set_volume':
profiles/audio/transport.c:2275:(.text.transport_bap_set_volume+0x11): undefined reference to `bt_audio_vcp_set_volume'
/usr/bin/ld: profiles/audio/bluetoothd-transport.o: in function `transport_bap_get_volume':
profiles/audio/transport.c:2266:(.text.transport_bap_get_volume+0x9): undefined reference to `bt_audio_vcp_get_volume'
Reported-by: Arun Raghavan <arun@accosted.net>
Fixes: af8266af13c8 ("audio: connect VCP profile client to MediaTransport")
Compare: https://github.com/bluez/bluez/compare/4d7d25b70245...c6dcf6b71450
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-09-17 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/master/4d7d25-c6dcf6@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.