ZuiMelanieForno

This is a tricky shit that hides behind openness, but in fact tightly controls the main part-the loader. I.e., at any time, it can block or completely control any unwanted person's actions.
 
 
It's funny, you described a whole theory about freedom, and as a result it all came down to advertising and pushing aml shit. 
For your information, aml imposes its BSP shit on everyone, which is stuffed with Trojans and bookmarks to gain full control over those who use their shit. They lie to all users about their hardware and actively cooperate with those you are trying to protect yourself from.
 
In general, everything is as usual, if you remove the beautiful words about freedom, it all came down to the fact that "someone" would spend their time and money and provide the rest with free use of aml shit.
 

@ZuiMelanieForno
 
Yes, Bluetooth works out of the box.

Hello all,
 
At this time all issues resolved. Thanks for the pointer from @SteeMan
 
I am running from SD Card.
Image Used: Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz
Uboot: u-boot-s905x2-s922 > u-boot.ext
dtb: /dtb/amlogic/meson-sm1-sei610.dtb - BlueTooth, HDMI Audio, WIFI Works, Ethernet does NOT work.
 
To get wifi working:
```
sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
sudo ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt
```
 
Additionally I have tested this dtb: meson-sm1-sei610-x96maxplus.dtb. Found from this below link.
 
BlueTooth, HDMI Audio, WIFI and Ethernet too work.
 
Admin you can mark this thread as SOLVED.
 
Thank you and kind regards
Hannah
 
 
 

@hannah You have a lot to learn about armbian on TV boxes and dtbs and kernels.  I plan to write a longer response this weekend when I have more time, but for now the short answer to your most specific question: no audio over hdmi is that you need to use a different dtb file.  Your box is s905x3 based (i.e. the sm1 architecture).  You are using based on what you reported a dtb for the s905x2 (g12a).  While much is the same, some things are also different.  Now what you may find is that if you use one of the very few available sm1 dtbs (I use and have only tested meson-sm1-sei610.dtb - the sei610 is the reference board for the s905x3 chip) that other things you have working on your current install (like wifi) will probably no longer work.
I believe you have likely already read the following: https://forum.armbian.com/topic/16407-please-read-first
as it was referenced in the last thread you started.  The current state for armbian on TV boxes is limited especially for amlogic cpus.  There are many reasons for this and that deserves a longer explaination of how dtbs and kernels interact and the overall goals of the armbian project.  (and how they differ from other projects out there like coreelec you reference above).
 
But I have already spent an hour of my day (we are all volunteers around here) setting up a test system to verify that audio does indeed work on a TX3 X3 box (as I thought it did, but because I don't normally run desktop environments as the current state of support really isn't working well yet, I didn't have an environment I could quickly test).  What I did just do is downloaded a clean copy of the 2020-10-14 balbes build of focal 5.9.0 desktop, used the meson-sm1-sei610.dtb and the u-boot-s905x2-s922 uboot file copied to u-boot.ext, booted and played the test.mp4 file and had correctly working audio via hdmi.  I then changed the dtb to meson-g12a-x96-max.dtb, which I believe you are using, rebooted and had no audio.
 
What I don't understand is that if you have read the Please Read First post, why you would post four posts in this thread within a day, seemingly demanding support for the 2 or 3 volunteers around here that monitor this forum?  Especially when you are asking about things like bluetooth, wifi, etc on the amlogic platform that we say you shouldn't expect to work, and if they do you are lucky.

del config kernel
 
CONFIG_RTL8822CS=m

Hello, sorry for replying so late, but didn't get the mention from your previous post.
 
The service file you quoted in that post contains the systemd service that activates the bluetooth userspace service.
It contains the invocation to hciattach
/usr/bin/hciattach /dev/ttyS0 bcm43xx 1500000 that will create the bluetooth device for use of other applications.
 
First you need the firmware file in the right place. Unfortunately hciattach is a legacy program, it wants the firmware file in /etc/firmware, so:
create the directory with mkdir -p /etc/firmware symlink the firmware wth ln -sf /lib/firmware/brcm/BCM4330B1.hcd /etc/firmware At this point I suggest you to do some tests using hciattach command above. You may need to modify the command line because /dev/ttyS0 device is the serial device the bluetooth is attached on rockchip boards.
You should first find which is the UART the bluetooth is attached to on your board. Be sure it is active in the device tree (so it is exposed as /dev/ttyS* file in the filesystem) and then change it in hciattach command line above.
Use hciconfig -a to see if the device is exposed to the system and hcitool scan to scan for bluetooth devices.
 
Once you have found the right serial device:
modify ap6330-bluetooth.service to use the right serial device copy ap6330-bluetooth.service file in /etc/systemd/system to make systemd aware of the new service, run systemctl daemon-reload to make the service run at every boot, run systemctl enable ap6330-bluetooth  
You can find the references in armbian scripts of above steps here