search

GloDroid / glodroid_manifest

Android port that aims to bring both user- and developer-friendly experience in using AOSP with a set of single-board computers (SBC), phones and other devices.
471 stars 67 forks source link

AOSP: Investigate UI component poor performance #62

Closed rsglobal closed 4 years ago

rsglobal commented 4 years ago

Recently I've found that Launcher3 and Status Bar (in expanded state) marks whole framebuffer as damaged. Even if very small amount of framebuffer is updated.

This can be observed by setting debug.hwui.show_dirty_regions=true property.

Android hwui has support for EGL_KHR_partial_update, which should be used to reduce load on GPU.

rsglobal commented 4 years ago

First step is to investigate does the dirty region forced to be full-screen on validation stage, or just framebuffer is drawn in such manner, Here is the link to validation code: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/libs/hwui/renderthread/CanvasContext.cpp;l=447;drc=master

rsglobal commented 4 years ago

Issue has been investigated. Dirty regions are displayed due to fade-in/fade-out full-screen effects. Closing as not a bug.