Amlogic-NO discussion

So will need to go with old firmware like before.
It mostly will only affect AV1 and VC-1 media.

For best possible support minimum firmware version 4.1 is need.

1 Like

A post was merged into an existing topic: OSD Video: Chapter display problem

If I go back to earlier builds speed goes up. If I up
date to 21 speed goes down?
Im confused too. :frowning:
I have repeated test 3 times.

EDIT:
i see borygo results :(. I will try the early dtb on the later one to see if there is any difference for me.
EDIT:
well… box updated to 22. Speed back :slight_smile:
No idea, but if it keeps working thanks to the CE team :wink:

1 Like

Vontar 905x4 no from 21 march.

1 Like

Thanks borygo. Im using the Kodi speedtest 3.1 version.
I will try a diff dtb just in case my Tox3 is playing silly buggers.

EDIT: as stated above, update to 22 and it seems to be working again :slight_smile:

I am really thankfull for the help I have been given :slight_smile:

I thought I will post here with an update. Despite my best efforts, the best firmware that I could find only brings ucode to version 3.55 and this was with late 2024 Vontar firmware - I even flashed the latest slimboxtv firmware for my box. I have not decided whether to buy a new box (maybe s928 for future proofing) or just run the box with amcodec hardware decoding disabled when trying to play AV1 videos on CE-NO. Another option is to revert back to CE-NE, which plays AV1 with hardware decoding

@Portisch Thanks for the latest nightly and my S905X4 (SC2) based box (X96max+ ultra) is able to play videos again. However the AV1 encoded video playback is still not working. The file below plays fine on my WIndows Kodi but not on CE NO running on S905X4 (SC2), The audio track plays fine but the video track is stuck on the first frame.
Can you please check if it plays on your end
https://www.mediafire.com/file/hrjx7oegra4il2v/Beast_-_Arabic_Kuthu.mkv/file
Thanks

Here is the screenshot where it works on Windows Kodi

No log, no problem, no help.
https://wiki.coreelec.org/coreelec:ce_support

The file plays perfectly fine on my S905X4 box (Dune Homatics R 4K Plus) using 0319 and last nights 0322.

If you’ve been following the thread, what’s your Android ucode version? Mine is 3.43 (from memory)which is less than the recommended. I can’t play AV1 but that doesn’t bother me.

@Portisch how do I find my android ucode version number, it flashed up briefly once in a notification I then updated Android and it’s never been displayed again.

So how do I know what it is?

Debug log:
jc -u opentee_linuxdriver
When there is no msg it should be ok.

Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: Android ucode version: '4.130'

Thanks :+1:

Actually that’s strange because that log say my ucode was 4.130 on the 6th of March however I updated to nightly 0322 this morning, 22nd March and it flashed a notification that my ucode version was only 3.8 so I’m not sure what’s happening there?

CoreELEC-NO:/ # jc -u opentee_linuxdriver
Mar 06 14:38:33 CoreELEC-NO systemd[1]: Starting opentee_linuxdriver.service...
Mar 06 14:38:33 CoreELEC-NO tee-loader[524]: run tee from android start
Mar 06 14:38:34 CoreELEC-NO tee-loader[524]: fw active slot: 'normal'
Mar 06 14:38:34 CoreELEC-NO tee-loader[524]: active slot: ''
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: Android ucode version: '4.130'
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: run tee from android end
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: tee from android match SCS version, trying from coreelec
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: cleanup tee start
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: cleanup tee end
Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: run tee from coreelec start
Mar 22 11:30:58 CoreELEC-NO tee-loader[936]: fw_path = /lib/firmware/video/video_ucode.bin
Mar 22 11:30:58 CoreELEC-NO tee-loader[936]: MM-module-name:Video firmware CA,Version:1.0.5-g3604ffd(build:958)
Mar 22 11:30:58 CoreELEC-NO tee-loader[936]: tee preload video fw ok
Mar 22 11:30:58 CoreELEC-NO tee-loader[524]: run tee from coreelec end
Mar 22 11:30:58 CoreELEC-NO dovi-loader[938]: run dovi 'start'
Mar 22 11:30:58 CoreELEC-NO dovi-loader[938]: loading dovi module from ce partition
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: filename:       /storage/dovi.ko
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: description:    Amlogic Dolby Vision Driver
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: license:        AML
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: vermagic:       5.15.137-android14-11-maybe-dirty SMP preempt mod_unload modversions aarch64
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: name:           dovi_gen_5_15_stb26
Mar 22 11:30:58 CoreELEC-NO dovi-loader[939]: depends:
Mar 22 11:30:58 CoreELEC-NO systemd[1]: Finished opentee_linuxdriver.service.

You life back in future.
The implementation was done 19.3.

No new Ucode version than 3.49 (Tanix W2)
What codec that won’t work below 4.1?
Many boxes do not have Android (Vontar X3, X96 Max, Tanix X4, etc.)- what can be done with these?

What?

If my ucode was 4.130 on the 6th of March then any version of CoreELEC I ran after that should of told me my ucode version was 4.130 not 3.8 like the 0322 nightly did. It’s got nothing to do with my life or the future.

It’s not possible to make a log from 6.3 when the code was implemented 19.3 :joy:

And yet the log is clearly date and time stamped as March 6:-

Mar 06 14:38:35 CoreELEC-NO tee-loader[524]: Android ucode version: '4.130'

I didn’t make the log on the 6th of March, I made it today but it contains a ucode version that is clearly date stamped as the 6th of March.

Read forum…