Amlogic-NO discussion

Ugoos S928X-J,K series devices larger than 3.49 boxes “Android ucode version: '4.101”

Do you have your journalctl spammed with invalid_dev id 13 as well?

Yes I also get that invalid dev_id spam after starting an h264 or h265 video mpeg2video seems ok.

Apr 05 16:54:04 CoreELEC kernel: [TEE] E/TC:4 invalid dev_id: 0x13

dtb: s5_s928x_x96_x10_8g

1 Like

And this will continue to be an issue forcing some people to purchase a new box maybe :frowning: if this is what they want. So far Im seeing CE still working ok in different releases working on older boxes so saving money and no waste. :slight_smile:

Thanks!
I looked, unfortunately I can’t use this ucode, it’s a bit different

The switch is useful when the hardware does support AV1 (s905x4 boxes), but the ucode is below 3.49. When this situation occurs, the current nightly just shows black screen but with audio for AV1 videos. If the idea for a switch is implemented, then it falls back to software decoding.

Have you looked at ucode from Homatics box r4k plus, which can be Android 12 or 14 (latest).

Just makes my Tox 3 play video side slooow.

Most S905X4 devices are stuck on Android 11, which is basically Kernel 5.4 (same as NE), so running the latest 5.15 kernel on NO and expecting the video ucode to be higher that 4.x is not going to happen at all.
CE 22 is deprecating NG and NE simultaneously which is sad. I totally understand deprecating NG as it is on Kernel 4.x.
However if Team CE consider supporting NE for the CE22 release it will helpout all S905X4 devices stuck on Android 11.
As mentioned before Kodi 20 and 21 should never have been released by TeamKodi, both are bug ridden mess. Kodi 22 has sorted out most issues and is shaping out to be a golden release. If only CE Team support CE22-NE, it will be fantastic. The next version of CE can deprecate NE release as by then the S905X4 devices would be ready for replacement with the S905X5

2 Likes

Agree, that makes sense.
At least should be one stable 22 release of CE-NE. So devices with older firmware still have an alternative.
Just one build and it doesn’t have to be officially supported.

1 Like

There will no CE-NE 22 as it doesn’t match together. The code base is to new for old devices and old sources. So it make just no sense. Stay with CE-NE 21, it will still run for years.

When people would have chosen a device from our supported vendors they would have ATV14 with ucode higher than required…

2 Likes

Tox3 is Ugoos. Ugoos is a supporting vendor.
Does that mean Tox3 is supported? Thanks :slight_smile:
https://wiki.coreelec.org/

Not all devices, no.
Supported devices have unique DTB.

Will GT King II have it ?
I was under the impression that not.
(Don’t want to fuel any discussion, as I’m happy with any CE version that supports HD audio on this box)

Such “generic” devices mostly not. They are a one setup, bought, setup, sell, done, next device…

I know the Homatics, Dune, VIM4, VIM1S and the S928X devices are on latest sources.

Sorry if this is a stupid question but I’m trying to understand the last few comments regarding ucode / ATV.

Why would people want to stay on NE when NO becomes mainstream? NO supports a lot more SoC’s than NE.

Is ATV14 a requirement for NO perhaps? But I see many people talking about devices on Android 12 running NO successfully so I’m confused.

1 Like

How do you do this? My system (android) is read-only.

Is there an alternative place for other ucode?

Seems issues arise with VC-1 and AV-1 playback on SC2 S905X4 with Hardware acceleration enabled. Can easily fix by turning off this function.

With NE no issues apparently.

Of the 2 Boxes i have that are SC2 A95XF4, HK1 RBOX S905X4 ,my concern is not AV-1 and VC-1 playback ,it is wifi/ bluetooth support.
These boxes are old with mt7668rsn and bcm 433X chipsets
No support in new Kernel 5.15.153, i dont think there ever will be,No Drivers.

So these boxes are best using NE for ever.!!!
I also do not have alot of AV-1 VC-1 in my library so really is not a factor.

1 Like

I’ve used the mt7668 wifi/bt drivers in CE-NO, they both work.

1 Like

Replace it in the firmware and then write it on the box with UBT.