Amlogic-NO discussion

Did not try; but how do you measure “quality results” to see the difference?

Cannot measure “quality results”. I have already said in my first comment above that in all formats and codecs the imge is “clearer” to my eyes and this makes it more enjoyable. This happens on my Panasonic LZ 1500 Tv. Then of course can be different opinions. This is my opinion after 2 days of watching any content without prejudice of any kind.

Clearer?

What hardware, which media source, and which was the “not clearer” b?

You are trying to see improvements in video playback quality, but this change is made for the screen capture feature.

Post nr. 2363:

Portisch CoreELEC Team

1d

Last nightly include a change for h264, h265, h266, vp9 and av1 decoder. We did enable double write mode and a picture improvement is expected.

And this is what I see “a picture improvement”

Why is so difficult to believe that I see picture improvement and is not a placebo effect?

Commit text media_modules-aml: Mode required for screen capture. Also no change for h264. See github.

I am not capable in technical arguments and do not understand what you say about commit etc. But I am referring mostly to H265 and AV1 coded movies/documentaries both in DV and HDR 10/10+

I see screen freezing sometimes with this “double write”- maybe video stream cache for playing from SAMBA NAS is not adjusted to this. I see many times 0 % in video stream cache. I checked not only last building of CE22NO, but also build from 09. september and there was cache at 67 % and for comparing in CE21NG is video cache stream at 99% (ugoos am6plus and identical video file in FHD with 1920x1080 in h264). This feature of double write “ for quality of better picture is clear 100 % placebo, but issue with video cache at CE22NO was strengthened and it is creating of screen freezing.

I have 2 boxes, a Tannix w2 (s905w2) and a no-name s905x2. Both get stuck in a boot loop on the nightly build 20250904. They work fine on the previous build 20250903. It seems the problem is caused by a kernel change from version 5.15.153 to 5.15.170. Has anyone encountered this problem?

You must start with last system, connect keyboard and photo taked outputs of error from commands: dmesg | less. This issue was in last december by changes version of kernel.

20250913 All key mapped controls work

20250915 Some key mapped controls (buttons) not working.

Reverted back to 913 all ok.

Key map Gen.xml file still present and correct

Tox3 S905x4

915 not working 100% key mapping https://paste.coreelec.org/RecheckDreamy

913 Key Key mapping OK https://paste.coreelec/RiddledAwfully

There were no changes for double write mode for h264. h264 always used double write mode 3

1 Like

Ok, so is new trouble of video stream cache.

I saw a screen freezing sometimes during playing and many times 0 % in video stream cache at CE22NO. I checked not only last building from 15. september of CE22NO, but also build from 09. september and there was cache at 67 % and for comparing in CE21NG is video cache stream at 99% (ugoos am6plus and identical video file in FHD with 1920x1080 in h264).

https://paste.coreelec.org/ChestEviction

https://paste.coreelec.org/FeederTempting

x88 pro x5m (s905x5m), after the latest update (I guess 20250915), AFR stopped working. Also, even on the content that matches the TV’s current mode (1920x1980@24p), there are many annoying micro-freezes and lags. Not sure about when exactly AFR stopped working, I don’t have many videos in non-24p framerate, but the playback of 24p content was smooth on the previous build.

I noticed that too. Went back to 20250913 and playback perfect. I really noticed it after I woke up the box from suspend. With 9/13 version, playback seems perfect for all frame rates I have. With 9/15, micro stutters are seen.

1 Like

Regarding double write mode, does the S905X4X chip SOC not support it?

Sorry for the stupid question, how do you go back to the previous version? Does that keep the user files?

20 seconds to find answer via GPT: ChatGPT - CoreELEC downgrade options

In CoreELEC, going back to a previous version (“downgrading”) is possible, but how it affects your user files depends on how you do it. Here are the main ways:


:counterclockwise_arrows_button: Method 1: Update folder (safe way)

  1. Download the older CoreELEC .tar image for your device (not the .img.gz, that one is for fresh installs).

  2. Copy the .tar file to your /storage/.update/ folder.

  3. Reboot the device. CoreELEC will detect the file and perform the downgrade.

:white_check_mark: This keeps your user data, settings, Kodi library, addons, etc. untouched.
:warning: However, if the database versions between Kodi builds differ (e.g. major version change), Kodi may not be able to read newer database files.


:counterclockwise_arrows_button: Method 2: Fresh reinstall (clean slate)

  1. Write the older .img.gz to your SD card or eMMC.

  2. Boot from it.

:warning: This will wipe everything unless you back up /storage/.
If you restore a backup from a newer version to an older version, some things may not be fully compatible.


:locked: User files safety

  • If you downgrade with the .tar method → your files stay.

  • If you reflash the whole system (.img.gz) → your files are erased unless backed up.

You can always back up manually:

scp -r root@device:/storage/ backup/

or use Kodi’s built-in backup add-on.

Go to this link:-

Index of /Amlogic-no/CE-22/20250913/

Then click on the larger file of the two entries (usually the first entry). This will download the .tar file for that date. Then just copy this file to /storage/.update/ folder on your device. I use WinSCP program to do this. Then reboot your CoreELEC device. This method will keep user files intact. You can use the ‘img.gz’ file this way also - by copying the file to /storage/.update/ folder and this will also keep user files intact.

Out of habit, I tend to use ‘img.gz’ files for new installs or upgrading releases (ie from CE 21 to CE 22 etc).

1 Like

I just upgraded to latest nightly (20250917) and so far playback has been smooth (even after waking from suspend). I have tried 23.976p, 24p and 25p files - no stutter yet.

2 Likes