The black screen saver does not turn off my TVs. I would like to have them turned of via CEC because of the power savings and reduced wear/tear. I am sure I am not the only one who might pause a movie, and become distracted by life. Saving power here and there adds up quickly over time.
Any chance of a backport so the Turn Off screensaver could work again?
CoreELEC already implements the fix linked above, and Turn Off screensaver is not a built-in part of Kodi, so I don’t understand what you expect us to do to fix it.
I will ask the dev of Turn Off if he will come over to this thread. Perhaps if we can get everyone in the same room, we can figure out where the problem actually is, and avoid this circular argument.
Above link to download this image is dead. Please check. Thanks.
It will be available later today. We still didn’t restore this subdomain since the recent server crash.
Okay tested it on a new sd, doesn’t seem to be working. Just in case somebody wants to know in the future
@cdu13a
I compiled an image from current amlogic-ng-on-gxl branch and I’m happy to report that the issues with the USB DVB tuner are now completely gone.
Ng now works absolutely great on Le Potato 1Gb.
The only issue I see is a very long pause (1 minute or something like that) before CE start to boot - that didn’t happen in previous Funhouse 4.9 builds.
@smp Thanks for the feedback. Sending you a test build to see if this issue was resolved on the 1GB Le Potato, was actually on my todo list for today. 
The long pause on boot is being looked at. I’ve got a few more of the developers on board for trying to make a push to get the GXL support merged into the main CoreELEC code base. So hopefully this and a couple of the other outstanding issues can get resolved and we can then add the GXL devices to the list of devices supported by the amlogic-ng build’s.
Is there any chance of getting a build that would work with the S805X / La Frite?
The La Frite board has some unique aspects to it that makes creating a CoreELEC build for it a bit more challenging, then what would normally be the case for other devices. I can try and take another look at creating a build for it, however I can’t currently give any timeline as to when that may be. 
Anything you could do would be greatly appreciated. It’s currently sitting on my desk next to an unused RPi, and it would be great to get it running CoreELEC.
Would appreciate a build on an S805 MXQ at you spare time.
The original S805 is Meson8 rather than GXL so probably wont happen. The S805X is GXL and effectively a nerfed S905X.
Hi!
Vontar x96 (s905x / RTL8723BS BT/WiFi )
working fine with gxl_p212_2g_slowemmc.dtb (BT/WiFi/Ethernet/CEC - all OK)
but with gxl_p212_2g.dtb have problem: first start with toothstick is OK but next after reboot have dark green screen and bootloop. If again start with toothstick - will OK but then after reboot green screen and bootloop again.
PS: On stable/night build I use gxl_p212_2g.dtb without any problem with reboot.
Not sure if this is specific to the GXL builds but I noticed that in 4K 50/60Hz modes it auto switch to 4:2:0 10-bit rather than 4:2:2. My TV can do 4:2:2 10/12-bit @4K 50/60.
dispinfo
The spec is 444 for 4K 24/30 and 420 for 4K 50/60.
The spec for 4K 50/60 is 4:2:0 10-bit and 4:2:0/4:2:2 12-bit. Why not use 4:2:2 12-bit?
There’s no benefit in 12bit or 4:2:2 for video playback except some potentially higher bandwidth requirements.
If you really want, you can force 4:2:2, although it would apply to all 4K refresh rates, including the lower ones.
Is this behavior hardcoded by amlogic? If not - can you point me in the right direction where exactly in the source code can this be tweaked?
And I don’t agree that there is no benefit. Although the source video is always 4:2:0 - we’d still want to deliver it to the display with as low losses as possible.
This has been how it is from the early days of the 4.9 kernel.
You can dig through the linux-amlogic repo for cdu13a’s commits.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice