rafman

FYI: in the meantime of Expecting some answer from bluez guys, I download / compile and install the latest version (5.78) of bluez from their site. With the latest version i have no ( TX Errors 0x0c24) (using either android or debian firmware) But now i have --> Bluetooth: hci0: Opcode 0x0c03 failed: -110 (on both firmware) and no discoverable Device. rafman@orion-8k:~$ dmesg|grep -i blue [ 6.263046] Bluetooth: Core ver 2.22 [ 6.263152] NET: Registered PF_BLUETOOTH protocol family [ 6.263158] Bluetooth: HCI device and connection manager initialized [ 6.263178] Bluetooth: HCI socket layer initialized [ 6.263188] Bluetooth: L2CAP socket layer initialized [ 6.263204] Bluetooth: SCO socket layer initialized [ 6.440666] Bluetooth: HCI UART driver ver 2.3 [ 6.440696] Bluetooth: HCI UART protocol H4 registered [ 6.440701] Bluetooth: HCI UART protocol BCSP registered [ 6.440805] Bluetooth: HCI UART protocol LL registered [ 6.440810] Bluetooth: HCI UART protocol ATH3K registered [ 6.440840] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 6.441010] Bluetooth: HCI UART protocol Intel registered [ 6.441112] Bluetooth: HCI UART protocol Broadcom registered [ 6.441146] Bluetooth: HCI UART protocol QCA registered [ 6.441152] Bluetooth: HCI UART protocol AG6XX registered [ 6.441182] Bluetooth: HCI UART protocol Marvell registered [ 6.764123] systemd[1]: Reached target bluetooth.target - Bluetooth Support. [ 6.813233] Bluetooth: hci0: BCM: chip id 68 [ 6.819051] Bluetooth: hci0: BCM: features 0x0f [ 6.842499] Bluetooth: hci0: BCM4334B0 [ 6.842526] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 6.854934] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch [ 12.833302] Bluetooth: hci0: BCM: features 0x0f [ 12.857635] Bluetooth: hci0: BCM4334B0 37.4MHz Class1.5 Samsung Note8-1675 [ 12.857665] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1718 [ 78.123328] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 78.123353] Bluetooth: BNEP filters: protocol multicast [ 78.123371] Bluetooth: BNEP socket layer initialized [ 78.126292] Bluetooth: MGMT ver 1.22 [ 80.164838] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 201.031249] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 271.432754] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 277.992897] Bluetooth: hci0: Opcode 0x0c03 failed: -110 rafman@orion-8k:~$ bluetoothctl hci0 new_settings: bondable ssp br/edr le secure-conn [bluetooth]# Agent registered [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC Pairable: yes [bluetooth]# version Version 5.78 [bluetooth]# power on [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC PowerState: off-enabling [bluetooth]# Failed to set power on: org.bluez.Error.Failed [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC PowerState: on [bluetooth]# discoverable on [bluetooth]# Failed to set discoverable on: org.bluez.Error.Failed [bluetooth]# exit rafman@orion-8k:~$ So i am Returning to bluez 5.66

My brcmfmac4330-sdio.transpeed,8k618-t.txt -> xtalfreq=37400

i did it. https://github.com/bluez/bluez/issues/980 I returned my firmware to original (Armbian) firmware files.

@Nick A After a lot of searching i found a thread with a similar problem (bug) on arch it started to happens (with 6.6.2 kernel) read here: https://bbs.archlinux.org/viewtopic.php?id=290578 my dmesg errors are same [ 27.873839] Bluetooth: hci0: command 0x0c24 tx timeout [ 27.873844] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 39.306413] Bluetooth: hci0: command 0x0c24 tx timeout [ 39.306412] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 41.322433] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 41.322455] Bluetooth: hci0: command 0x0c24 tx timeout I don't know if it remains and affects us.

You are here. main.conf

I do the same and the adapter seems to work fine now (better than before) rafman@orion-8k:~$ sudo hciconfig -a hci0: Type: Primary Bus: UART BD Address: 00:0E:42:C3:DC:50 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1945 acl:0 sco:0 events:129 errors:0 TX bytes:4194 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Name: 'orion-8k' Class: 0x6c0000 Service Classes: Rendering, Capturing, Audio, Telephony Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x0 LMP Version: 4.0 (0x6) Subversion: 0x410d Manufacturer: Broadcom Corporation (15) but i have no discovery results. Something is problematic with BCM4334B0.hcd or with the driver / patch.

your device is not descoverable give : [bluetooth]# discoverable on and retry with your phone.

replace the BCM4334B0.hcd (don't delete it) / Reboot When is powered on --> (Changing power on succeeded) give : discoverable on USE your mobile phone, activate bluetooth, end discover for devices. can you see your TV-box from your mobile ? if yes then it work as mine.

your adapter is not powered. sudo bluetoothctl power on you receive (Changing power on succeeded) or error ?

if vontar has the same chip Every information/log will be usefull. But i don't have any live android (Transpeed-k8-t box). I attach here my partial working firmware files, if you want to test it with your kernel. part-working-fw.tar.gz

On Android the vendor use this values to configure BT on device however i don't know if this information will help us. vendor/etc/bt_configure_rf.ini vendor/etc/bt_configure_pskey.ini I attach the files. bt_configure_pskey.ini bt_configure_rf.ini

Hmm Unpacked Firmware files for Bluetooth, seems to be the same and on newer firmware. But this time i will share the whole vendor/etc folder because i see that it contains some configuration files about bt and wifi and other hardware from the vendor so probably we may extract very useful information about box configuration by study on it. You can download it here : https://easyupload.io/sdd0a0 My current Bluetooth state is this: rafman@orion-8k:~$ bluetoothctl Agent registered [bluetooth]# show Controller 43:34:B0:00:1F:AC (public) Name: orion-8k Alias: orion-8k Class: 0x00000000 Powered: yes Discoverable: yes DiscoverableTimeout: 0x00000000 Pairable: yes UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0542 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name

Negative / Crash I have deleted everything from my /lib/firmware/brcm and i reverse the android (fw) now i have only theese files and bluetooth working as previous. rafman@orion-8k:~$ ls -l /lib/firmware/brcm/ total 512 -rw-r--r-- 1 rafman rafman 53957 Jan 1 2009 BCM4334B0.hcd -rw-r--r-- 1 rafman rafman 457249 Jan 1 2009 brcmfmac4334-sdio.transpeed,8k618-t.bin -rw-r--r-- 1 rafman rafman 2019 Jan 1 2009 brcmfmac4334-sdio.transpeed,8k618-t.txt -rw-r--r-- 1 rafman rafman 2019 Jan 1 2009 brcmfmac4334-sdio.txt I will unpack/decopmpose now the newer android firmware . (H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.17.20.img)

@Lancoly You are still working with miniarch. Note: Don't expect to much power from X96q-H313 if you need more capabilities consider to buy a transpeed-8k (4/64) However, We also have advanced here. Armbian now boots now for your 5.1 board ! and Ethernet is working. You can try this image for your board: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_24.11.0-trunk_X96q-v5-1_bookworm_current_6.6.44_mate_desktop.img.xz I also have compiled an image Here: https://easyupload.io/58pgrm (but this is for secure boot boards and may not booting to your board)

Results. 1> The original BCM4334B0.hcd from my Armbian image does not work, and i think has same behavior as the LibreElec BCM4334B0.hcd. 2> Firmware from LibreElec works only with the wifi but not with Bluetooth. 3> The android firmware works but not stable (I am not 100% sure about the Android firmware file) i used to extract it because i did not Flash this firmware to my device, however from my internet search i found that many variations of transpeed-8k h618 box exists arround. NOTE: There is also a newer version of android firmware (H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.17.20.img) that i will investigate today to see if some firmware is different. 4> I think the "sdio.txt" is the nvram file (nvram_ap6334.txt) and i already test it (as is) by copy to /lib/firmware/brcm and as brcmfmac4334-sdio.transpeed,8k618-t.txt but this did not make any changes. I am taking this information about interface (android fw): rafman@orion-8k:~$ sudo hciconfig -a [sudo] password for rafman: hci0: Type: Primary Bus: UART BD Address: 43:34:B0:00:1F:AC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:5156 acl:0 sco:0 events:603 errors:0 TX bytes:56764 acl:0 sco:0 commands:619 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Can't read local name on hci0: Connection timed out (110) This is my TV, with Mate Desktop (customized)

I will try for more tomorrow. it seems to do be a mater of firmware however this firmware works but not stable. With previous firmware a was not able to discover any device. however and with android firmware I have tx errors. FYI : I attach my dmesg files for both situations with original (before) and (android) original fw files was also from LibreElec collection. but i will check tomorrow if something is different in your link above. android-fw-dmesg original-fw-dmesg

Firmware is not stable Bluetooth adapter is not powered correctly.. sometimes works but not stable and lot of tx errors.

I rename: the files and copy it to /lib/firmware/brcm bcm4334.hcd --> BCM4334B0.hcd fw_bcm4334b1_ag.bin --> brcmfmac4334-sdio.transpeed,8k618-t.bin nvram_ap6334.txt --> (as is) to /lib/filrmware/brcm/ it seems to work for me now (i can see my mobile phone on discovery) but i still have tx errors on dmesg.

I will check it ... now i am in progress Download the files Here: https://easyupload.io/wab7ki Firmware Contains: ( For transpeed 8k HK6334Q these files are suspected) bcm4334.hcd fw_bcm43341b0_ag.bin fw_bcm43341b0_ag_apsta.bin fw_bcm43341b0_ag_p2p.bin regulatory.db regulatory.db.p7s

I finally extract it is on vendor/etc/firmware The android firmware file is (H618.apollo-p3.T-H618_100M_12.2022.12.05.23.41.img) You can download the extracted full firmware files here : https://easyupload.io/wab7ki

I have the same output as MMorales on 6.7.12 but ..( probably this is valid and for 6.10.x) kernel asks for an additional firmware blob file: (but i can't find it) --> (probably is filtered from dmesg of MMorales) [ 6.169613] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2 I Formated my emmc on my box but i found a firmware however there are many variations of such boxes Additionally: Super partition is dynamic partition not an ext4 i Have convert Super.fex with simg2img to raw image but i can not mount it... We need A live box. @MMorales Do you have any working Android firmware for your box ?

I already do this right now, and i have also installed Armbian on eMMC. i give the command sudo halt the system halts, and after boots normally (when i unplug and re-plug the power cable) on sudo reboot no problems. FYI: when my system Was on SD Card i remember (but not always) sometimes i had problem to boot when the keyboard and mouse was connected to tv-box but when i removed both the usb cables the problem was solved.

I did not test with other kernel previous to 6.7.12 however 6.7.12 seems to be stable for me. But I had problems switching to newer kernels like 6.10.9. (no boot at all) i will make further checks with 6.7.12.

This probably is because the kernel and / or the u-boot patches. You can try my compiled image (burn it to a seperate SD card) and test it (I Tested on Transpeed 8k 4/64) You can Download it Here : https://easyupload.io/j19vgs Don't try to switch kernel because it will break, just download the headers from above link. and install it with sudo dpkg -i <deb_file > and then you can compile openvfd.

use: cat /sys/class/hwmon/hwmon0/temp1_input |awk '{printf "%.2s", $1}'