royk

@luizkunThen you're not running it directly from the login screen. It should show gbm. If the video is really not hdr I don't know why it doesn't show the video under Wayland, but I guess it will work under gbm.

@luizkunThe Kodi amazingfate has build is using GLES. What do you see in Kodi at: Settings -> System info -> Video -> Windowing system

I did also have these problems at the beginning, but I don't have seen them for about a month I think. No sure what made the difference, I thought it was because there were some changes made in the drivers/kernel code. I changed some settings in the kernel config, like disabled most of the debugging options, default scheduler at performance, timer at 1000hz, set the compiler at performance and some other settings with the scheduler. Maybe this fixed the lockups? Although this probably won't make a difference for the behavior of the cursor, or could the timer clock at 1000hz have reduced the flickering? There are some minor problems like night light doesn't always work immediately but does start after I turn on the receiver or reboot the tv.

hdmi dummy adapter, I don't know anything else

Perhaps you've installed something for nvidia? Check: apt list --installed *nvidia* if you find something from nvidia and remove with sudo apt remove ....

Did you set: Enable legacy vnc protocol with "require password" filled in a username and password Updated the package Try to connect with ip address instead of hostname Maybe there is a firewall in between or another service on the OPI running on the same port?

From the gui. Settings -> Sharing -> Remote Desktop You could update it with sudo apt install gnome-remote-desktop

I don't know with what you try to connect it to, if you try to connect with vnc then "Enable legacy vnc protocol". It could be that the notification to accept the client was not visible, you could set "Require password" (3 dots after legacy vnc protocol) as workaround.

@luizkunDid you set the settings in Kodi as how amazingfate has in his instructions? After starting kodi (from login screen), in Settings -> Player -> Videos, enable "Allow using DRM PRIME decoder" and "Allow hardware acceleration with DRM PRIME". And set "PRIME Render Method" to "Direct To Plane"

Nice! The gnome-remote-desktop should work, you probably already have it installed.

sudo apt remove dkms wget http://imola.armbian.com/beta/pool/main/l/linux-5.10.110-rockchip-rk3588/linux-image-legacy-rockchip-rk3588_23.02.2_arm64.deb sudo dpkg --force-all -i linux-image-legacy-rockchip-rk3588_23.02.2_arm64.deb sudo reboot sudo apt install waydroid sudo waydroid init

wget http://imola.armbian.com/beta/pool/main/l/linux-5.10.110-rockchip-rk3588/linux-image-legacy-rockchip-rk3588_23.02.2_arm64.deb sudo dpkg -i linux-image-legacy-rockchip-rk3588_23.02.2_arm64.deb wget http://imola.armbian.com/beta/pool/main/l/linux-5.10.110-rockchip-rk3588/linux-headers-legacy-rockchip-rk3588_23.02.2_arm64.deb sudo dpkg -i linux-headers-legacy-rockchip-rk3588_23.02.2_arm64.deb What is the output of cat /var/lib/dkms/anbox-binder/1/build/make.log

I would say that the deb have the kernel modules inside or built-in You could try this first: sudo apt update && sudo apt reinstall linux-image-legacy-rockchip-rk3588 Otherwise the default config on github has these already enabled.

You could check the config of the installed kernel, if these modules were already enabled, then it won't help if you rebuild with that same config nano /boot/config-5.10.110-rockchip-rk3588

sudo apt install linux-image-legacy-rockchip-rk3588 If you build one yourself the debs will be in ./output/debs/ To install sudo apt install ./*image*.deb or sudo dpkg -i *image*.deb

I guess you need these kernel modules: CONFIG_ANDROID_LOW_MEMORY_KILLER=n CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDERFS=y CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder" These are in the config on github, probably you'll need to update the kernel

@MarcAndro https://gitlab.freedesktop.org/wayland/weston/-/issues/467

@luizkunPerhaps you're trying to play a hdr video in Wayland? AFAIK hdr doesn't work in Wayland, you should run Kodi directly from the login screen. https://forum.armbian.com/topic/24802-kodi-for-rk35xx-510-legacy-kernel/

Did you also update the kernel? About the flickering cursor, I've seen that the cursor has been moved from hw to software because some had problems with a disappearing cursor. Maybe it's because of the resolution/refresh rate you're using?

I've tried a hdmi to vga adapter on a beamer and this one works at least: Amazon link If you didn't already you could try different resolutions/refresh rates for the HDMI/DVI cable

After updating the chromium-browser and gpu drivers I'd also a high cpu usage. After searching for way too long I realized that chromium-browser was running under xwayland. To set it back to Wayland: chrome://flags/ search for "Preferred Ozone platform" Set to Wayland The cpu usage is back to around 10/15% while playing 4k YouTube video again.

About the DVI adapter, maybe it's an uni directional one for the wrong direction?

Recompile the kernel with exfat support git clone https://github.com/armbian/build.git && cd build ./compile.sh BUILD_ONLY=kernel KERNEL_CONFIGURE=yes BOARD=orangepi5 BRANCH=legacy Then search for Filesystems and then I thought another submenu enable exfat and compile In the output/debs folder it places the packages. You could also try to compile/install the exfat kernel module from: https://github.com/arter97/exfat-linux git clone https://github.com/arter97/exfat-linux && cd exfat-linux make sudo make install sudo modprobe exfat

Are you trying to run it with Wayland? You could try Remote Desktop.

That's great, now @amazingfate has created a package for moonlight-embedded as well as for Moonlight -QT I guess he earned the $ 1000,- like you've promised?