Is this considered hardware acceleration?
No, KMS isn't the actual hardware acceleration layer:
Is this considered hardware acceleration?
No, KMS isn't the actual hardware acceleration layer:
Sorry I didn't see the VP9 in the logs...
Line 8 of your log snippet. YouTube often plays ads before the actual content, so maybe the ad is VP9. VP9 was developed by Google, so it would make sense.
Update to LE 12.
We don't work with log snippets. Provide a complete one.
what is difference between 'video=HDMI-A-2:D' and 'video=HDMI-A-2:d', upper and lower case Dd?
modedb default video mode support — The Linux Kernel documentation
Maybe creating new EDID helps:
Update to latest LE to get latest Bluetooth drivers. If the problem remains...
I’ve come to the conclusion that the tv in our RV has an issue outputting the media.
Or you're using a cheap cable over there. Make sure it's conform to HDMI 2.0 / 2.1 standard.
when i install the (none legacy) generic will i get HDR?
Yes.
I guess your PC has an LSPCon chip to convert from DP to HDMI. Those chips have known driver issues, and such issues are very likely unsolvable by us (search for "LSPCon" on the forum).
Make sure your BIOS is up-to-date. If your hardware support page offers video driver updates, install the latest. They sometimes include firmware for the LSPCon driver. You probably need Windows to install those updates.
You probably get your videos from illegal sources, and they aren't encoded correctly:
2024-08-02 17:51:35.042 T:881 debug <general>: ActiveAE::SyncStream - average error of 102.118088, start adjusting
2024-08-02 17:51:35.092 T:881 debug <general>: ActiveAE::SyncStream - average error 2.118088 below threshold of 30.000000
...
Feb 27 17:26:21.857301 Lanser kernel: v3d fec00000.v3d: MMU error from client CLE (4) at 0x6dc1000, pte invalid
Feb 27 17:26:25.549369 Lanser iwd[410]: invalid HE capabilities
Feb 27 17:26:25.549889 Lanser iwd[410]: error parsing non-HT rates
Does Android use OpenGL or Vulkan for this?
Android supports OpenGLES and Vulkan. I don't think it's used pretty much, because they use a lot of hardware acceleration for video playback. RPi does the opposite: It uses a lot of software decoding, which needs more processing power.
So both platforms might deliver the same performance on different hardware.
When using the Generic (non-Legacy) LE, it should work like that:
Replace "keyboard" by "remote" at file name and XML tag.
You can change the power button behavior by key mapping. Create a keyboard.xml file. Example:
So is it some kind of miscommunication between LE and LG TV? Who can tell...