Testing on a N2+ with tone mapping HDR to SDR, since my TV does not support HDR in a meaningful way. Trying any DV file results in a crash, sometimes in a minute or two, sometimes after playing a good half an hour of the video.
As suggested by another user here, rolling back to 20250409 solves the problem, and indeed i verify problem is solved (The tonemapping however is VERY VERY different than latest nightly, very bright and contrasty) I let it play the same files, never crashed.
I’ve updated my s905x3 generic box to newest nightly (20260426) and now it doesn’t boot, it keeps crashing (boot loop). Previously I had (20260414) version.
Sadly archive.coreelec.org seems to be down. Does anyone have mirror for older nightly builds?
On my s905x4, it also booted up not on the first try, but on the second (the first time in the entire month I’ve been using CE-NO). The first boot was in safe mode, a reboot helped, and then everything worked as expected. A log file with FAILED in the title appeared, for the first time.
There was a bug found today releated to the last HDMI hotplug commit.
So it was possible a crash + reboot can happen directly on boot.
So best is to try next nightly again - as always.
Also good news for S928X, S905X5M & S905X5 devices: The GBM GUI tearing is finally fixed and gives now same quality like on devices before using GBM libMali.
With today build and i see 100% using of cpu and higher temperature during playing at Ugoos am6plus. And last month i see longtime a crash of CE after playing videos during cca 4 hours.
AM9Pro user here, starting with one of last week’s NO-nightlys the BT remote (G20S Pro BT) started acting up (was working perfectly until then). Sometimes it has a long delay, sends numerous commands in a row and after a while stops working completely.
I am not at the device at the moment but can send a log later today, if considered helpful.
Other than that, the NO-Nightlys are working perfectly on the AM9 Pro - Thank you to the developers!!!
Well, my N2 and N2 plus d vices do the same thing since some nighlies. Haven’t found time to produce some logging as it happen very randomly. It’s a freeze followed by a reboot.
If I get some free time I will get to it to get this solved.
That is not a clean install, save effort for the devs trying to find issues and test with a clean install so issues can Only be attributed to CoreELEC.
