蓝牙控制器配置文件

蓝牙控制器配置文件

在 中bluetoothctl,如果我show在默认的蓝牙控制器上运行,我会得到以下信息:

Controller XX:XX:XX:XX:XX:XX
        Name: computer-name
        Alias: computer-name
        Class: 0x00010c
        Powered: yes
        Discoverable: no
        Pairable: yes
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0517
        Discovering: no

支持的蓝牙配置文件(例如 A/V 远程控制)在哪里设置?它是来自我的 USB 蓝牙适配器的固件还是来自 bluez 堆栈中的某个位置?我可以更改配置文件以支持新的配置文件吗?

答案1

我发现可以通过提供适当功能的程序添加额外的蓝牙配置文件。因此,如果我在计算机上设置蓝牙 OBEX 服务器,则show该命令的输出bluetoothctl会有一堆新行:

Controller XX:XX:XX:XX:XX:XX
        Name: computer-name
        Alias: computer-name
        Class: 0x10010c
        Powered: yes
        Discoverable: no
        Pairable: yes
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        Modalias: usb:v1D6Bp0246d0517
        Discovering: no

第一次设置时,我执行了类似以下步骤的操作(配对之后,连接之前):

sudo killall bluetoothd
sudo bluetoothd --compat
sudo hciconfig hci0 up
bt-obex -s [/path/to/receiving/directory]

然而,现在我似乎只需要运行最后一步,这实际上启动了 OBEX 服务器。我不确定现在其他步骤是否必要。

相关内容