Frozen frames

Frozen frames are UI frames that take longer than 700ms to render. This is a problem because your app appears to be stuck and is unresponsive to user input for almost a full second while the frame is rendering. We typically recommend apps to render a frame within 16ms to ensure smooth UI. However, when your app is starting up or transitioning to a different screen, it's normal for the initial frame to take longer than 16ms to draw because your app must inflate views, lay out the screen, and perform the initial draw all from scratch. That's why Android tracks frozen frames separately from slow rendering. No frames in your app should ever take longer than 700ms to render.

To help you improve app quality, Android automatically monitors your app for frozen frames and displays the information in the Android Vitals dashboard. For information on how the data is collected, see Play Console docs.

Frozen frames are an extreme form of slow rendering, so the procedure for diagnosing and fixing the problem is the same. For information on diagnosing and fixing slow rendering, see slow rendering.

Note: The Android vitals dashboard and Android system keeps track of frozen frames for apps that use the UI Toolkit (the user-visible portion of the app is being drawn from Canvas or View hierarchy). If your app does not use the UI Toolkit, as is the case for apps that are built with Vulkan, Unity, Unreal, or OpenGL, then frozen frames and other render time statistics are not available in the Android Vitals report. You can determine if your device is logging render time metrics for your app by running adb shell dumpsys gfxinfo <package name. However, note that even if that command produces any output it may only cover some of the rendering in your app, but not all of it.