Which system do you use? Android, Ubuntu, OOWOW or others?
Android 14
Which version of system do you use? Please provide the version of the system here:
edge2-android-14-v250708.img
Please describe your issue below:
We intend to use the Edge2 in an unattended kiosk installation with a Unity application targeting 30 fps.
Depending on the connected TV, automatic HDMI detection can select a high refresh rate. When this happens, the Android boot animation plays noticeably slower, and the Unity application and video playback perform considerably worse.
With automatic selection, we observed:
Resolution: 2560x1440
Physical refresh rate: 100 Hz
Active render frame rate: 25 fps
Forcing 2560×1440 at 60 Hz fixes the issue:
adb root
adb shell setprop persist.vendor.resolution.HDMI-A-0 "2560x1440p60"
adb reboot
After reboot:
Boot display mode: 2560x1440 at 60 Hz
Active render frame rate: 30 fps
The boot animation then plays at normal speed, HDMI detection is faster, and the Unity application runs significantly better.
However, we cannot hard-code 2560x1440p60 because the kiosk may be connected to TVs with different native resolutions and aspect ratios, including 1920×1080, 2560×1440, 3840×2160, and ultrawide formats.
Is there a supported way to use the display’s native EDID resolution while limiting or preferring the physical HDMI refresh rate to 60 or 59.94 Hz?
Android’s minimum and maximum refresh-rate settings do not change the physical HDMI mode during early boot. An application-side fix would also be too late because the slowdown already affects the Android boot animation.
We found this related topic:
Edge2 Android 14: HDMI display not properly detected during boot
Unfortunately, the test image is no longer downloadable.
Could this change also affect automatic high-refresh-rate selection? If so, could you provide a current download link or an updated Android 14 image containing the change?
Alternatively, is there a property or firmware configuration that automatically selects the display’s native resolution at 60 Hz?
The final system must configure itself automatically because no ADB access will be available after deployment.