简体繁体 English

为什么在使用低功耗蓝牙时必须停止蓝牙？

[英]Why must bluetoothd be stopped while using Bluetooth Low Energy?

原文 2019-05-08 01:05:41 2 1 bluetooth-lowenergy/ bleno

I have implemented a BLE peripheral. 我已经实现了BLE外设。 The device is based on Ubuntu OS. 该设备基于Ubuntu OS。

My application runs under Node.js. 我的应用程序在Node.js下运行。 It uses bleno ( https://github.com/noble/bleno ) to advertise its BLE service. 它使用bleno（ https://github.com/noble/bleno ）宣传其BLE服务。

According to the read-me file at the site, in order to offer BLE services, daemon bluetoothd must be stopped and optionally disabled. 根据站点上的自述文件，为了提供BLE服务，必须停止并可选地禁用守护进程bluetoothd 。

This statement seems to be true as my app works as expected only when this daemon has been stopped. 该语句似乎是正确的，因为仅当此守护程序已停止时，我的应用程序才能按预期运行。

I am curious as to why must bluetoothd daemon be stopped. 我很好奇为什么必须停止bluetoothd守护程序。 I couldn't find any explanation on the net. 我在网上找不到任何解释。

1 个解决方案

BlueZ with bluetoothd is the built-in Bluetooth system for Linux that is the default. BlueZ和bluetoothd是默认的Linux内置蓝牙系统。 KDE and Gnome user utilities use this. KDE和Gnome用户实用程序使用此功能。 There is also an API at https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/gatt-api.txt for GATT. 在https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/gatt-api.txt上还有一个用于GATT的API。

Now, bleno is a "hack" that implements a Bluetooth host itself and therfore needs to completely take over the hci controller. 现在，bleno是一个“ hack”，它本身实现了蓝牙主机，因此需要完全接管hci控制器。 In order not to interfere with bluetoothd, bluetoothd must be stopped. 为了不干扰蓝牙，必须停止蓝牙。