Try an earlier version 1st.
Drop into Update folder https://archive.coreelec.org/Amlogic-no/CE-22/20250511/
If still an issue go back to standard (in corelec settings) and add what you did if its ok and see if same error occurs.
Team CE have indicated that they will only support S905X4 boxes running Android 13 or later for CE22 due to Amlogic enforcing newer ucode requirement on the Amlogic 5.15 kernel
CE22 will run on boxes with older Android but will not decode AV1 and VC1
CE21-NE runs on fine with AV1 and VC1 hardware acceleration on these boxes and Team CE have indicated that there wont be a CE22-NE release. The last CE22-NE nightly they worked on was from Dec24 which now seem to have been removed from archive.coreelec.org.
So your best bet for the Android 11 TV Box is to stick to CE21-NE or if you want CE22 get a S905X4 device running Android 13 or above
Team CE didnāt decide this. The AV1 & VC1 decoding code used by CE-NO comes from Amlogic, and that 5.15 code requires ucode version 3.49 or newer. This ucode file is part of the Android firmware. The older the Android version, the older itās ucode version.
A fews week ago someone posted in this thread he updated the video_ucode.bin of the latest Vontar X4 firmware, I have also done so by using MIK4.3Build3107 (can be found on 4PDA, the version on Github is older and does not work). I used the video_ucode.bin from the TOX3_3.5.241108 firmware.
So now my Vontar X4 has:
CoreELEC-V tee-loader[531]: Android ucode version: ā3.49ā
Sorry, not dissing Team-CE. it is Amlogic to be blamed here as they suddenly killed support for the older ucode on the 5.15 Kernel starting around March/April 2025.
Do you have now av1 and vc1 by kernel 5.15?
If it is only the digits of the version, it is possible to return 3.49 or higher simply when checking the version.
@YadaYada did maybe found a work around to load also new firmware on devices with older Android firmware below 4.1. So if this works AV1 and VC1 should start working on them.
A good amount of credit goes to @gjstroom that gave me the idea that thereās some flexibility that CE can work with. We should be able to do away with any ucode version problems all together on any CE devices. It will take a day or three to get something out thatās polished.
In my brief tests, this should fix AV1/VP9/VC1 and some DV playback issues on devices running older ucode.
Iām interested to know if it just.a pure version number problem, or there is something really in that binary (or other binaries in the firmware if you have to replace many of them) that manages av1 vc1.
Itās probably safe to assume that there are changes in the binary. Thereās nothing nefarious going on. Things are just complicated because CE is covering many different box models (different SOCs), with different Android versions, with different version TEEs. Android boxes use a single unified firmware that covers one device model, itās more simple.
Are you using the MIK tool suggested above. If so, just drop and drag the *.img file onto the open window. The video_ucode.bin file will be in the same directory as the img file. Navigate to /super/vendor_a/vendor_a/lib/firmware/video to find the file
