Thomm

On an OrangePi-5b, `apt-get update` a few days ago updated the kernel, and now bluetooth no longer works. What's the proper way to downgrade the kernel to whatever I had before? (armbian-config shows way too many options)? Better yet, get it working again? bluetoothctl does not see the controller at all, and dmesg gives the following: $ dmesg|grep -i bluetoo [ 2.796188] Bluetooth: Core ver 2.22 [ 2.796203] NET: Registered PF_BLUETOOTH protocol family [ 2.796206] Bluetooth: HCI device and connection manager initialized [ 2.796211] Bluetooth: HCI socket layer initialized [ 2.796214] Bluetooth: L2CAP socket layer initialized [ 2.796220] Bluetooth: SCO socket layer initialized [ 3.925419] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 122. [ 3.925433] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 102. [ 3.925438] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 22. [ 3.925590] input: bt-powerkey as /devices/platform/wireless-bluetooth/input/input5 [ 23.055720] Bluetooth: HCI UART driver ver 2.3 [ 23.055728] Bluetooth: HCI UART protocol H4 registered [ 23.055730] Bluetooth: HCI UART protocol BCSP registered [ 23.055731] Bluetooth: HCI UART protocol ATH3K registered [ 23.055769] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 23.055873] Bluetooth: HCI UART protocol Intel registered [ 23.055911] Bluetooth: HCI UART protocol Broadcom registered [ 23.055921] Bluetooth: HCI UART protocol QCA registered [ 23.055922] Bluetooth: HCI UART protocol AG6XX registered [ 23.057998] Bluetooth: hci0: sending frame failed (-49) [ 23.058029] Bluetooth: hci0: Opcode 0x1003 failed: -49 [ 23.177045] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 23.177063] Bluetooth: BNEP filters: protocol multicast [ 23.177077] Bluetooth: BNEP socket layer initialized

More attempts: As suggested by DeepSeek (ChatGPT was less helpful), I also tried changing the bluetooth service script to ExecStart=/usr/libexec/bluetooth/bluetoothd --noplugin=a2dp --noplugin=avrcp --noplugin=player and then restarting systemd itself and the bluetooth service, but no luck. I tried adding monitor.bluez.properties = { bluez5.roles = [ ] } to /usr/share/pipewire/pipewire.conf and restarting wireplumber, but no luck. I tried menu advertise uuids 0x1200 0x1800 0x1801 0x180a in bluetoothctl, to disable advertising the audio profiles, but no luck. But when in bluetoothctl, it really shows the audio connection being made when the phone connects.

I'm using Bluetouch in my iPhone as a bluetooth mouse (rarely when needed) for my OrangePi/Armbian/Kodi setup. All fine with that… except… with my iPhone paired to the OrangePi, it also connects all its audio to the OrangePi, *all the time* when in range, unless I completely disable bluetooth from the iPhone. According to the only instructions I've found, I've tried setting [General] Enable= in `/etc/bluetooth/main.conf`, and restarting the bluetooth service, but the only effect this has is that there's no audible output. The phone still connects its audio to the box, just with no audible output. How to completely disable Armbian from advertising itself as a bluetooth audio device, while being able to connect bluetooth peripherals?

Has anyone managed to get Armbian on Orange Pi 5(b) output audio through the 3.5mm jack? The device seems to be recognised, but even after fiddling with everything imaginable through alsamixer, with speaker-test running in the background, I am unable to actually get any sound out. HDMI audio works without any problems. ChatGPT thinks it has something to do with GPIO routings not being properly set up. I'm running Armbian 25.2.3 noble (through `apt-get dist-upgrade`; I had to first install an older version from the archives to avoid bricking when installing on the eMMC). $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchipdp0 [rockchip-dp0], device 0: rockchip-dp0 spdif-hifi-0 [rockchip-dp0 spdif-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchiphdmi0 [rockchip-hdmi0], device 0: rockchip-hdmi0 i2s-hifi-0 [rockchip-hdmi0 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: rockchipes8388 [rockchip-es8388], device 0: dailink-multicodecs ES8323 HiFi-0 [dailink-multicodecs ES8323 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0

Any updates on this? I am just trying to install Armbian on the eMMC of 5B. It’s not working, so I ran into this thread. If possible, I wouldn’t want to open the case (and undo the thermal tape) to access the maskrom button, so I was wondering if the you think the instructions of sns1801 could be adapted to constructing a new image with several invocations of dd? Then use any image on an SD to flash the custom image from a USB stick using dd?