We are in AM9 thread 
Maybe same issue happen with one fw in the past and we had to make changes. And now fw made changes again and we have to make them again.
Hello everyone. I haven’t posted here in a while… Thanks to issues with DTB in the 2.2.0 firmware (AM9 Pro), I accidentally discovered BD3D support and was a bit shocked, in a good way. I had completely forgotten about 3D on Amlogic, but it turns out I shouldn’t have. I wish the developers success and will test your new products in the background whenever possible, as I don’t always have access to the box. Simply put, I can test BD3D whenever I have free time.
@vpeter Thank you very much, CE 22 is working properly AM9 Pro V2.2.0 now using new dtb file.
I assume this images was not made on official build right?
Well the point is that the issue is present,probably this tonemap HDR to DV thing need some adjustments,otherwise it cuts deep blacks.
But I guess this is the last thing CE team will try to fix,since we would benefit using HDR>DV from like watching only some none existent MDL 4000 movies like Mad max:fury road.
99% HDR movies now are MDL 1000 and if it needs more nits the DV layer is already present.
Maybe your solution is to contact Dolby Vision direct as they are the author of the VS10 stuff?
I am sure they do know how to handle it correct.
Can a dev take a look at this issue?
where can I download the new dtb
https://discourse.coreelec.org/t/ugoos-am9-pro-soc-s6-s905x5-j/58183/399
But it should be already in every Update.
Amlogic SoC S905X (GXL) or older will no longer be supported by CoreELEC 22.0-Piers.
est ce que cela signifie que ma Ugoos Am9 pro n’est pas compatible ?
Does that mean my Ugoos Am9 Pro isn’t compatible?
I’m asking because I get a black screen with a mouse pointer when I boot it into recovery mode. The Ugoos firmware is up to date.
Thanks in advance
That´s not true.
Please read forum
I’m sure it is not: you need version 2.2.0.
Hi, i m in 2.2.0. I’ve updated to the latest nightly build before the beta
Did you reboot to android after update?
Yes, to check that the update had gone through successfully.
CoreELEC-Amlogic-no.aarch64-22.0-Piers_beta2-Generic.img
I flashed my microSD card with this file, renaming it to dtb.img in the root directory, and added my dovi.ko and the remote.conf file for ur02 to the root directory.
Then I used the recovery method
Here is your mistake: you need latest nightly build (first supported build is 20260910). Read few posts above regarding new Android version.
Hi @Portisch, hi @vpeter and Team,
Following up on the successful deployment of the new S6 DTB on the latest v22.0 nightly (which perfectly fixed the local Ethernet/LAN and frame-buffer initialization after updating the internal eMMC Android firmware to v2.2.0), there is still a critical regression regarding external USB DAC audio synchronization.
Hardware Setup: Ugoos AM9 Pro (S905X5-J / 4GB DDR5) connected via USB to an SMSL DAC (Thesycon XMOS Systemsoftware, Hardware ID: 152a:85dd).
The Issue:
Every time the system undergoes a soft reboot or a hard power cycle, the ALSA kernel subsystem completely drops the USB DAC mapping. During the early boot phase, it seems the Amlogic S6 USB controller executes an aggressive ACPI power-down/reset cycle on the USB bus. Since Kodi initializes faster than the device re-enumeration handshake, the ALSA soundcard index shifts, and CoreELEC defaults the audio output back to HDMI, completely dropping the USB audio selection.
Diagnostic logs (lsmod | grep snd and aplay -l) return an empty profile immediately after reboot, even though the device is physically present on the bus (lsusb correctly detects the Thesycon ID 152a:85dd).
As a temporary workaround, adding a raw sleep 4 and forcing modprobe snd-usb-audio via autostart.sh helps occasionally, but the underlying kernel USB audio handshake is highly unstable on this new S6 architecture. Since very few users are running high-end external DAC architectures on the S905X5-J, this bug could easily go unnoticed.
Could we get a permanent kernel-level fix to ensure the USB soundcard enumeration index remains locked during early boot phases?
Thanks for your incredible dedication.