It’s not exactly a reproducible issue, so making a clean install is unlikely to help. It’s just one of a few similar crashes I’ve seen so I grabbed a log to share here in case it’s useful. If it doesn’t help, nevermind.
If it’s not reproducible and you haven’t followed the pre check then all you’re doing is adding noise.
Not intended to be harsh only factual.
I have a spare one I will prep when I can
does any s922x user know what is the latest nightly that does not have this kernel panic crashes? CE is currently unusable for me. rolling back to latest alpha i lose tvheadend since the latest version does not work with latest tvheadend.
On my ‘prod’ systems the beta3 release doesn’t show the issue
On my Beelink GT King with nightly build April 1, 2026, i have no crashes and a working wifi at startup.
I believe that the random reboots started with 22.0-Piers_nightly_20260410
So the 22.0-Piers_nightly_20260405 I think is the last one that was kinda stable
This is on a ODroid N2+ , I have a GT King Somewhere I will see if I can locate it.
Tearing is gone. Thank you for your work. ![]()
I was looking commits of this release but did not find commit solving the tearing issue. archive.coreelec.org/Amlogic-no/CE-22/20260428/changelog-20260428.html
Could you please mention which commit it is?
HDMI CEC Issue
When I turn off the TV, the soundbar turns off and works properly, but
when I turn on the TV and the soundbar, the screen stays black and there is no sound. I have to restart the SK1 or my other devices.
Everything works fine on Android, Kodi, and Enigma2 devices.
The system is connected via ARCH.
I have this issue as well. I have the Ugoos AM9, I have been experiencing this since last year.
I felt it was a skin issue, as this was also occurring on android also.
Pretty much what you said would occur. If I stream a show for about an hour, pressing stop could cause the os screen to freeze, if it didn’t freeze there pressing the menu button to jump back to main menu (Aeon Nox Silvo p3i) would freeze as the widget and menu bar where moving into position.
What I was going to do was capture the logs and get an AI to analyse to give me an idea of what might be causing the issue.
Now since I’m not the only one seeing this issue, I think I’ll do as suggested by others and creat a clean build with no skin change and see if the issue can be captured
Tearing start with build from 28.april 2026 at ugoos am6plus. Build from cca 5 april 2026 was last stable (no restart after watching more videos).
22.0-Piers_nightly_20260429
Beelink GT King
Random reboots, Kernel Panics log below
https://paste.coreelec.org/ColorsBloated
Sample used was
https://www.libde265.org/hevc-bitstreams/sintel-1080-cfg02.mkv
So I prepped a N2+ with latest nightly, minimal adjustments.
Player has been happily playing in a loop during the night, asking me to update this morning:-/
Will be adding things I need gradually to see when it’ll panic again. Might take a while…
For the G12B, S922X users:
is last one working 20260314? And 20260317 not anymore?
It works with s922xj at build 5 april 2026 without issue. I will put her some logs from ugoos am6plus. But i have question to possibility a reset of old logs from data from build of 28 april 2026.
On next build 10.4 it changed the double write mode.
So reset it after boot with current nightly to like before 10.4:
echo 0 > /sys/module/amvdec_h264/parameters/double_write_mode
Which one is next which doesn’t work? 20260410 ?
The one where the reboots started for me is nightly_20260410
that is on a N2+
5.april
Now in this moment i will only start of playing during watching many videos - stability test at random reboot
https://paste.coreelec.org/GalvinAinsley
https://paste.coreelec.org/Followupjoins
and after echo 3 > /sys/module/amvdec_mh264/parameters/double_write_mode
https://paste.coreelec.org/DeniaGorge
https://paste.coreelec.org/BomberDownfall
- april - start issue of random restart (today veriefied with testing! - i go again longtime test only at build of 5. april)
https://paste.coreelec.org/ScrambleLeeloo
https://paste.coreelec.org/ExhaustRuins
https://paste.coreelec.org/ChargedCramps
After
echo 3 > /sys/module/amvdec_mh264/parameters/double_write_mode
echo 0 > /sys/module/amvdec_mh264/parameters/double_write_mode
https://paste.coreelec.org/GazingTissue
https://paste.coreelec.org/CloneConduct
- april
- called tearing and higher using of cpu (100% at one core during h264/h265 playing of video) and very high temperature Amlogic-NO discussion - #3409 by atirage21
https://paste.coreelec.org/MidgeHandsome
https://paste.coreelec.org/PenguinGloria
- april - it seems staying 100% in case of one cpu core, and cpu have higher temperature is in relation to online streams (not to local files). Tearing is not by online streams in compare to build from 28 april. It need more time for testing of random restart (also during playing of local files), but here from 28 april build is temeperature issue by online streams video as extra
After CoreELEC:~ # echo 0 > /sys/module/amvdec_mh264/parameters/double_write_modeCoreELEC:~ # echo 0 > /sys/module/amvdec_mh264/parameters/double_write_mode
https://paste.coreelec.org/ResidentAlbania
https://paste.coreelec.org/ClogsReaching
https://paste.coreelec.org/StuffFerrari
Try before playback
echo 0 > /sys/module/amvdec_mh264/parameters/double_write_mode