OrangePi 3 LTS - Bluetooth not working

[kris777]

Wi-Fi works → so the problem is only in GPIO / DTB initialization for Bluetooth

It worked on the older kernel, but now it doesn't 😞....

Supposedly this is the cause, but is it really?

Quote

DTB (device tree) does not configure GPIO reset/power for the UWE5622.

hci_uart cannot initialize the controller → hci0 is not created.

The overlay for BT in mainline 6.x does not yet exist in Trixie.

❌ Result: hciconfig -a and bluetoothctl list show nothing.

armbianmonitor -u

https://paste.armbian.com/uzudezufit

Edited yesterday at 07:05 PM by kris777

[c0rnelius]

Which kernel? Should work on 6.12.y, although I see issues with it on 6.18.y, as there were changes made to that wireless patch set that don't agree with my DTS changes.

In fairness, I haven't checked to see if it works at all regardless of my changes on that kernel though. Its on my list of things to investigate.

 

The new DTS changes require an updated hciattach_opi binary. "known to work on 6.12.y"

https://github.com/armbian/build/blob/main/packages/blobs/bt/hciattach/hciattach_opi_arm64_upstream

 

[kris777]

 armbianmonitor -u in the link it shows : https://paste.armbian.com/uzudezufit

Linux version 6.12.74-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #6 SMP Thu Feb 19 15:29:56 UTC 2026

Edited yesterday at 07:28 PM by kris777

[c0rnelius]

I'm not seeing any bluetooth error, are you?

 

rfkill unblock all

 

[c0rnelius]

Welcome to Armbian! 

Documentation: https://docs.armbian.com | Community support: https://forum.armbian.com

IP address: xx.x.x.xx 

Create root password: *****
Repeat root password: *****

Developer Preview Build

This Armbian image was generated automatically for development and testing purpose.
It may include unfinished features or unstable components.

If you are not here to report issues or just test it, please do not use this image in production.
Expect things to change — or even break — as improvements are made.

Creating a new user account. Press <Ctrl-C> to abort

Please provide a username (eg. your first name): 
Disabling user account creation procedure

root@orangepi3-lts:~# rfkill
ID TYPE      DEVICE         SOFT      HARD
 0 bluetooth bluetooth unblocked unblocked
 1 wlan      phy0      unblocked unblocked
 2 bluetooth hci0      unblocked unblocked
root@orangepi3-lts:~# bluetoothctl
[NEW] Media /org/bluez/hci0 
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 30:96:18:9E:A7:02 Pairable: yes
hci0 new_settings: powered bondable ssp br/edr le secure-conn 
[bluetoothctl]> show
Controller 30:96:18:9E:A7:02 (public)
	Manufacturer: 0x01ec (492)
	Version: 0x09 (9)
	Name: orangepi3-lts
	Alias: orangepi3-lts
	Class: 0x00400000 (4194304)
	Powered: yes
	PowerState: on
	Discoverable: no
	DiscoverableTimeout: 0x000000b4 (180)
	Pairable: yes
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0554
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x10 (16)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedSecondaryChannels: 1M
	SupportedSecondaryChannels: 2M
	SupportedSecondaryChannels: Coded
	SupportedCapabilities.MinTxPower: 0xffffffec (-20)
	SupportedCapabilities.MaxTxPower: 0x0008 (8)
	SupportedCapabilities.MaxAdvLen: 0xfb (251)
	SupportedCapabilities.MaxScnRspLen: 0xfb (251)
	SupportedFeatures: CanSetTxPower
	SupportedFeatures: HardwareOffload
[bluetoothctl]> exit
root@orangepi3-lts:~# uname -a
Linux orangepi3-lts 6.12.74-current-sunxi64 #6 SMP Thu Feb 19 15:29:56 UTC 2026 aarch64 GNU/Linux

 

[kris777]

That's strange  🙂 ...we have the same kernel. Maybe something's broken in the system? But I haven't messed with Bluetooth in the system. I've only updated the system: apt update /apt upgrade /reboot 🙂

 

root@orangepi3-lts:~# rfkill
ID TYPE      DEVICE         SOFT      HARD
 0 bluetooth bluetooth unblocked unblocked
 1 wlan      phy0      unblocked unblocked
..............................
bluetoothctl
Waiting to connect to bluetoothd...
it keeps reading but shows nothing?
...................
 bt-device -l
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Aborted
.............

Something must have broken in the system, but what and where?

 

Can you give me the exact: Armbian image + version ...

Contents of ..../lib/firmware/uwe5622/

also: armbianEnv.txt

Output dmesg | grep -i uart i dmesg | grep -i bluetooth

Maybe that will help me figure out where the errors are in my system? Or maybe I have Debian and you have Ubuntu?

Ps. or, more simply, information from the file: diagnostics.txt

command in terminal:

.................

(
uname -a
cat /etc/os-release
ls -lh /lib/firmware/uwe5622/
lsmod | grep -iE "bt|sprd|uwe"
dmesg | grep -i uart
ls /dev/tty* | grep -i "ttyS\|ttyAMA\|ttyBT"
cat /boot/armbianEnv.txt
rfkill list
hciconfig -a
bluetoothctl list
hcitool dev
bt-device -l
dmesg | grep -iE "bluetooth|uwe|sprd|hci"
) > diagnostics.txt

.....................

Edited 49 minutes ago by kris777