BlueZ-4.101 RFCOMM issue and missing daemons
I'm setting up BlueZ-4.101 to run on my 3.3 linux kernel. I've run into a few issues with development involving pairing with another device.
The first issue is RFCOMM. I'm trying to use the command Code:
# rfcomm connect 0 After further inspection, I see that /dev/rfcomm0 (or any rfcomm node) does not exist after using the command Code:
# rfcomm bind all This investigation led to me seeing that I am missing some bluetooth scripts that should possibly be running. I'm not quite sure if I should or should not have these scripts based on my kernel/bluez version. For example, the only daemon that I have is bluetoothd which I start on boot. I do not have any of the following scripts even installed:
To me, this feels like I have something possibly configured incorrectly in the kernel/filesystem. However, I've checked and made sure that I have full support for Bluetooth, including: Kernel:
Filesystem:
I've tried to solve this for days and could use a little guidance. If more information is needed let me know. Relevant information: /etc/bluetooth/rfcomm.conf: Code:
# Code:
# hciconfig -a: |
Regarding the missing /etc/bluetooth/hcid.conf file, I see now that this thread addresses that. The other issues still persist however.
|
Updating with another log file, as I'm still having trouble but have more information.
Some things that I've noticed but am not sure what to think of:
Code:
#bluetoothd -d -n |
Audio support with bluez4.101
Hi,
I would like to know if you were able to get anything working on bluez4.101 since I am also exploring bluez4.101. I am particularly looking into audio streaming capabilities using bluez4.101. -- Praneet |
I ended up doing a whole OS upgrade and using BlueZ 5.46 and kernel 4.12.0. Things are generally working well with that setup.
|
All times are GMT -5. The time now is 04:03 AM. |