Make BlueZ DBus peripheral the default backend on Linux

The DBus backend was introduced in Qt 6.5, and is intended as
the eventual successor of the kernel backend. Users can opt-out
and use the older kernel backend by setting the
QT_BLUETOOTH_USE_KERNEL_PERIPHERAL environment variable.

[ChangeLog][QtBluetooth] The default Linux peripheral implementation
was changed from the kernel interface to the BlueZ DBus interface.
The old implementation remains available by defining
QT_BLUETOOTH_USE_KERNEL_PERIPHERAL as environment variable.

Fixes: QTBUG-115925
Change-Id: I27d60e410c02d0435c7dce81e5c06448a89bcc65
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

1 files changed, 0 insertions, 7 deletions

diff --git a/examples/bluetooth/heartrate-server/doc/src/heartrate-server.qdoc b/examples/bluetooth/heartrate-server/doc/src/heartrate-server.qdoc
index e3e625aa..342fe058 100644
--- a/examples/bluetooth/heartrate-server/doc/src/heartrate-server.qdoc
+++ b/examples/bluetooth/heartrate-server/doc/src/heartrate-server.qdoc
@@ -31,13 +31,6 @@
     To visualize what it is doing, you can use the \l {heartrate-game}{Heart Rate Game}
     example, which is basically the client-side counterpart to this application.
 
-    \note By default on Linux a kernel socket API is used for advertising, which
-    means that a privileged access is required to start advertising. This can
-    be achieved by running the example as root, for instance via \c sudo.
-    Starting from Qt 6.5, an alternative approach is to use the BlueZ D-Bus
-    backend for advertising, which does not require root access. To enable
-    this backend, set \c QT_BLUETOOTH_USE_DBUS_PERIPHERAL environment variable.
-
     \section1 Checking Bluetooth Permission
     Before the application can create a service and start advertising, we have to check
     if the application has a permission to use Bluetooth.