Closed cocarrig closed 2 years ago
We have narrowed this issue down to only the chromium-browser application, and believe the hardware acceleration in the updated 92.x release added in 2.26 is causing the artifacts.
We are reviewing the necessary steps to change hardware acceleration settings in the browser to resolve the issue.
Additional chromium flags needed to support chromium 90+ have been identified below: --use-gl=desktop \ --enable-features=VaapiVideo-decoder \ --ignore-gpu-blocklist \ --enable-gpu-rasterization \
Updating and creating new release with updates to complete UAT.
Unfortunately, the updated flags necessary for Pi4 use are not usable for non Pi4 deployments. A different solution will be developed to open the browser with appropriate flags for both systems.
Solution has been developed to review if the device is a PI4 inspecting /proc/device-tree/model. If the device is a Pi4 it will add the following Chromium flags: --use-gl=desktop --enable-features=VaapiVideo-decoder --ignore-gpu-blocklist --enable-gpu-rasterization
This has been added into release 2.31 which is pending UAT at this time.
UAT Passed, closing issue. Release is available for download at the following link: https://drive.google.com/uc?id=1v30upy-eYuPBhh0Y6D3O2Lk_5rdTLOrN&export=download
Describe the bug White blocks appear intermittently on RPi4 systems inside the DAKboard screen rendered via the chromium-browser.
To Reproduce Steps to reproduce the behavior:
Expected behavior Artifacts on screen such as white blocks should not display
Screenshots N/A
Device Type (please complete the following information):
DAKboard OS Version (please complete the following information): 2.26-2.29
Additional context N/A