ATV 13 - android.hardware.drm / MESA failing #8
Description
So just tried the ATV 13 image.
Hardware DRM errors
It seems in android 13 there some substantial changes in how hardware is handled. Either way this results in blank screens in most apps, including youtube and even drminfo.
This was at least working with the ATV 11 image (with software rendering because VAAPI with AMDGPU was not working.)
10-03 19:19:16.274 2402 2688 W HidlServiceManagement: Waited one second for android.hardware.drm@1.0::IDrmFactory/clearkey
10-03 19:19:16.274 19 19 I hwservicemanager: Since android.hardware.drm@1.0::IDrmFactory/clearkey is not registered, trying to start it as a lazy HAL.
10-03 19:19:16.275 2402 2688 I HidlServiceManagement: getService: Trying again for android.hardware.drm@1.0::IDrmFactory/clearkey...
10-03 19:19:16.479 0 0 E init : Control message: Could not find 'android.hardware.drm@1.0::IDrmFactory/clearkey' for ctl.interface_start from pid: 19 (/system/bin/hwservicemanager)
10-03 19:19:16.275 19 9714 W libc : Unable to set property "ctl.interface_start" to "android.hardware.drm@1.0::IDrmFactory/clearkey": error code: 0x20
10-03 19:19:16.275 19 9714 I hwservicemanager: Tried to start android.hardware.drm@1.0::IDrmFactory/clearkey as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
...
10-03 19:30:51.849 2118 2136 W MESA : Using gralloc header from libdrm/android/gralloc_handle.h. This is not recommended for new distributions. Initializing a fallback gralloc as a helper:
10-03 19:30:51.850 2118 2136 I MESA : Using fallback gralloc implementation
10-03 19:30:51.851 2118 2136 W EGL-MAIN: failed to get driver name for fd -1
10-03 19:30:51.851 2118 2136 W EGL-MAIN: MESA-LOADER: failed to retrieve device information
10-03 19:30:51.851 2118 2136 W EGL-MAIN: failed to get driver name for fd -1
Thats a very unhappy Mesa, probably because it doesn't have the AMD drivers.