Using Bluetooth #92
-
|
I've successfully installed pi deploy and it works great, but I'd like to use the Bluetooth functionality of my phone. When listing the Bluetooth adapter using the bluetoothctl command no adapters can be found, but when listing the adapters via rfkill it can see the bluetooth adapter of my phone. Is it possible to enable or mount the Bluetooth adapter somehow? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Hi... If you enable bluetooth tethering Android will assign an IP to the BT interface. |
Beta Was this translation helpful? Give feedback.
-
|
When running You won't see the Bluetooth TCP/IP interface until you either enable tethering or Bluetooth PAN... see here for an example: |
Beta Was this translation helpful? Give feedback.
-
|
I've enabled it in the android settings but I still don't see it listed. |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to setup the Bluetooth integration for Home Assistant which installed through Pi Deploy. The setup wizard doesn't work because it doesn't detect any Bluetooth adapters. I'm running this through an S7 edge which has a bcm4359 WIFI/Bluetooth combo chip. I've ran hciconfig, bluetoothctl, dmesg grep -i blue, and rfkill with Bluetooth tethering on and off which all return nothing except for rfkill, which does show a Bluetooth device. I've also tried connecting a Bluetooth adapter via an OTG cable with no output as well, but it does show up in lsusb. I've also tried debian 10 and 12 which also doesn't Work. I'd really appreciate some help. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunantely I don't think you're going to be able to achieve what you want to accomplish, not easily at least. Android uses a different bluetooth stack (Fluoride or Gabeldorsche) than what's available in normal Linux. That's why the container isn't responding to BT commands in the way you'd expect. You can use the |
Beta Was this translation helpful? Give feedback.
-
|
Ah I see, that's unfortunate. Thank you for the reply. |
Beta Was this translation helpful? Give feedback.
Unfortunantely I don't think you're going to be able to achieve what you want to accomplish, not easily at least.
Android uses a different bluetooth stack (Fluoride or Gabeldorsche) than what's available in normal Linux. That's why the container isn't responding to BT commands in the way you'd expect.
You can use the
unchrootcommand to escape the container and play with the Android BT stack directly, for example trysudo unchroot dumpsys bluetooth_manager