Ugoos AM9 Pro - SoC S6 S905X5-J

I’m experiencing some issues. I haven’t reported them yet because I can’t provide a log from my current location.

  • Video playback from my [SMB] server fails with an error.

  • YouTube trailer previews display a black screen.

  • Loading a debug log fails.

But since it seems to be working for others, I wanted to make sure I had done things correctly beforehand.

No, log, request invalid.

Addon, not CE related.

Fixed already.

In sum invalid support request…

From today’s build 20260306 there is separate dtb for this device named s6_s905x5_ugoos_am9_pro.dtb. Please use this one which has at least fix for a LED for now which works the same way as on non Pro version.

@ragico: this applies to you too :wink:

3 Likes

It works perfectly. No more that fastidious led light. Thank you @vpeter and all the CE stuff. As usually you make a great job.:grinning_face:

2 Likes

I also tested the new dtb for the Ugoos AM9 Pro.
The dtb works correctly and allows proper control of the status LED color and brightness, thanks to the corrected mosi-gpios configuration. At this point, a big thank you to the developers.

For anyone who wants to experiment with it or adjust the behavior on their system, here are some details.

  1. LED node in the dtb
    The relevant section is the /led node:
    /led {
    compatible = “amlogic,sk9822_led”;
    status = “okay”;
    sck-gpios = <0x1d 0xa 0x0>;
    mosi-gpios = <0x1d 0x5b 0x1>;
    active-color = <0x01003000>;
    suspend-color = <0x01000090>;
    shutdown-color = <0x00000000>;
    };
    The status LED is controlled via an SK9822 controller.

  2. Color value format
    Colors are defined as 32-bit values in the format:
    Example from the dtb: active-color = <0x01003000>
    You can read the current values in CoreELEC with:
    cat /sys/devices/platform/led/colors/*
    Example output: active color is 1 00 30 00

  3. Value meaning

    1. Brightness (1–9)
    2. Red
    3. Green
    4. Blue
  4. Testing colors live (no reboot required)
    The LED can be controlled directly via sysfs.
    Example: red at lowest brightness
    echo “1 ff 00 00” > /sys/devices/platform/led/colors/active

  5. Persistent settings via CoreELEC (autostart.sh)
    Changes via /sys are not persistent and will reset after reboot.
    To apply settings automatically, create:
    /storage/.config/autostart.sh

  6. Setting colors directly in the dtb
    Alternatively the colors and brightness can be defined directly inside the dtb.
    :warning: This requires a custom compiled dtboutside the official CoreELEC release.
    Example:
    active-color = <0x02000040>;
    suspend-color = <0x02400000>;
    shutdown-color = <0x00000000>;

  7. Disabling the LED completely
    Inside the dtb:
    status = “disabled”;
    or simply set all colors to 0:
    active-color = <0x00000000>;
    suspend-color = <0x00000000>;
    shutdown-color = <0x00000000>;

I’m having an issue playing 4K DV movies (I tried several). The movie starts playing but I only hear the audio, the screen is black.

These files worked fine on my old S905X device. But now on the AM9 Pro they won’t play.
Same TV, same receiver, same HDMI cable, same NAS.

I have tried forcing to 4:2:0, it did not help.

Other media plays fine, it seems like the issue only manifests with 4K DV.

  • Firmware 2.0.6.
  • CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260306-Generic.img
  • Using dovi.ko linked above in the thread.

Logfile attached. This is from a completely fresh install, the only setting I changed was enable the remote control via bluetooth.

kodi.log (1.0 MB)

  1. display does not support DV, DV system is disabled
  2. the file you played does not contain DV information (is not DV)

Does it work if you turn off refresh switching?

Settings → Player →Adjust display refresh → Off

2 Likes

Thanks! Yes, with display refresh: off it plays everything I throw at it, it just does it at 1080p 60fps :slight_smile:

Great!

I’ll leave the rest for Team-CE

1 Like

Make clean install without any modification.
Place correct dovi.ko.

Start one playback after boot with your issue.
Run dmesg | paste.

1 Like

2 posts were merged into an existing topic: Amlogic-NO discussion

14 posts were split to a new topic: Ugoos AM9, HDR only green on Sony TV

I have an SK1 device.

I installed CoreELEC 22 Alfa3

and used the dovi.ko file.

However, I cannot play any movies.

Only a black screen appears.

Is there a solution?

Did you upload the correct dovi file?

Hello, I found an issue on the latest nightly with Ugoos AM9 Pro. If I play a Dolby Vision file that has an L5 active area set for top and bottom (so it’s not 0-0) then the player’s navigation bar (interface) gets invisible because the L5 value is cut off. The functions are working (I can stop, pause etc) but I don’t see the buttons.

A few nightlies ago this could be resolved by setting the “override L5 with 0” option in the Display menu, but now that’s not working anymore. I see the difference in the brightness of the black letterbox bars when I change this setting but the player’s navigation bar won’t reappear.

And the sample?

Samples to test DoVi L5 metadata:

Tron Legacy Imax - 1st half is cropped, second half is full 2160p, navigation bar is hidden then it reappears

Tron Ares Imax - whole sample is cropped but 2nd half is Imax so black bars are thin, navigation bar gets mostly visible

Sinners Imax - 1st half is cropped, second half is full 2160p, navigation bar is hidden then it reappears

Was anyone able to test it yet?

Hi !

I’d like to share my impressions of the AM9 Pro running CoreELEC 22.0-Piers_alpha3, having previously used Khadas Vim 4: Overall, it’s very stable, boots up very quickly, and has the widest range of format support I’ve seen so far (only Profile 7 FEL is missing). Unfortunately, the graphics performance is far below that of Vim 4, making it impossible to display the interface in 4K (the frame rate is too low). Furthermore, the screen tearing (vertical desynchronization?) present even with the GUI upscaler makes for a very unpleasant user experience.

Therefore, I’ve decided to stick with VIM4 for a while longer, even though this issue is likely due to a graphics driver problem. In any case, I’d like to thank the developers for their work.

vim4 is raspberry PI type hardware, is that correct?

Khadas Vim 4 : Amlogic A311D2 SBC