incbot

I am need to sleep more)) I stubbornly answered "y" instead of "yes" when pairing with the phone in bluetoothctl )))) It turned out to connect on "yes". 😀😀😀 Say me please an exists easier way to solve the my problem with Bluetooth?

I tried to do the following: 01) replace the driver (do symb link): ln -s /usr/lib/firmware/brcm/BCM43342.hcd /usr/lib/firmware/brcm/BCM.hcd. 02) Judging by armbianmonitor -u, the chip was recognized. 03) Installed the necessary packet: sudo apt install bluetooth -y 04) Tested that the service Bluetooth is running: sudo service bluetooth status. 05) Got "Running" 06) Only after these actions hciconfig -a gave a meaningful conclusion... 07) Next, after all this, I tried to control bluetooth via : sudo bluetoothctl 08) On the show command inside, I finally saw my device wiyh MAC and that it was active. 09) Put it into detected mode: discoverable on 10) Saw the alias rk3318-box on my phone when searching for Bluetooth devices around. 11) Despite the fact that an invitation with the same PIN code for connecting appeared both on the tvbox and on the phone, for some reason it is not possible to connect them. At the same time, for the tvbox mode Pairable: yes !!! THE REASON IS NOT CLEAR TO ME, but it is definitely associated with tvbox, because as soon as I confirm the connection (press "Y") on it, the connection is cut off... Phone confirmation does not interrupt the connection at first. WTF? I reinvent the wheel again????? PS After pair coomand on tvbox i see it: [agent] Confirm passkey 815681 (yes/no): y Failed to pair: org.bluez.Error.AuthenticationFailed

All the data above was collected after installing the necessary overlay in rk3318-config and then rebooting...

I turned off overlay rockchip-RK3318-box-wlan-ap6330 in armbian-config (not a single overlay was selected here anymore) and selected the rk3318-box-led-conf1 option through rk3318-config (in this case, overlays rk3318-box-led-conf1 and rk3318-box-wlan-ap6334 are connected to boot). A certain Bluetooth block appeared in the text of the armbianmonitor -u output (see new output here), but apparently the driver is still not the same and hciconfig -a does not work (there is no command in the system). Any more ideas?

Good day JOCK. Thank you so much for linking to the latest armbian releases. I installed 25.5.0-trunk.444 and brought it to 25.8.0-trunk.26 by several updates. The system is loaded and steadily updated. Managed to configure ethernet and wifi with static addresses. The network works well. The question is that I can't figure out how to start bluetooth. At first, the system worked without overlays and tried to load BCM43342 when I connected overlay 6330 using armbian-config, nothing changed. I don't have too much experience in unix. What am I doing wrong? PS I attach a photo of the board and armmonitor -u)

Thank you very much. As usual I tried to get into the wrong car)) I will try

Good day people. Tell me, there is an ancient 4k ULTRA HD PRO 2/16 Gb H96MAX box (blue board). After installing armbian 23.08.0 on it, everything works well RIGHT AWAY even without using overlays. However, after apt upgrade, armbian25.2.3 arrives and the system hangs at boot. The inspection showed that in/boot/dtb/( in reality it is/boot/dtb-6.3.13-rockchip64/rockchip) there is no hardware tree). Moving the hardware tree from 23.08.0 allows the system to boot, but hdmi hangs (by ssh the system works, but the screen of the real console hangs). In addition, WiFi is no longer visible (it is not in the settings at all), connection is possible only by RJ45. Question: are there any chances to make 25.2.3 work normally (and what is needed from me for this) or just fix the system on 23.08.0? PS Many thanks to the community for working image 23.08.0