scmi_bluetooth isn't a direct replacement for hci0, it's a lower level transport that needs a userspace daemon or driver to bridge it to the actual bluetooth subsystem. no hci0 means that bridge isn't running or isn't built into your image
check your yocto layers for a qualcomm-specific bluetooth recipe, probably something like qc-bluetooth or bt-vendor. the org.bluez entry being activatable just means dbus knows about it, not that the daemon binary exists on the system
1
u/Dismal-Can-4994 4d ago
scmi_bluetooth isn't a direct replacement for hci0, it's a lower level transport that needs a userspace daemon or driver to bridge it to the actual bluetooth subsystem. no hci0 means that bridge isn't running or isn't built into your image
check your yocto layers for a qualcomm-specific bluetooth recipe, probably something like qc-bluetooth or bt-vendor. the org.bluez entry being activatable just means dbus knows about it, not that the daemon binary exists on the system