[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-05-21。"],[],[],null,["# Android vitals helps Google improve the quality of Android apps on Google Play.\nWhen a user allows it, their Android-powered device tracks app quality metrics\nsuch as stability, performance, battery use, and permission issues. Google Play\ncollects this data, which can be accessed through the [Android vitals\ndashboard](https://support.google.com/googleplay/android-developer/answer/9844486?visit_id=637804734146240317-4134883661&rd=1) in the [Play Console](https://play.google.com/console/about/), and through the [Google Play\nDeveloper Reporting API](https://developers.google.com/play/developer/reporting).\n\nDevelopers should monitor Android vitals to improve the user experience,\nespecially the core vitals: **user-perceived crash rate** ,\n**user-perceived ANR rate** , and **excessive partial wake locks**.\n\nCore vitals and bad behaviors\n-----------------------------\n\nYour app's core vitals affect your app's visibility on Google Play. Each core\nvital has an **overall** bad behavior threshold and a **per-device** bad\nbehavior threshold.\n\n### FAQs\n\n#### What are core vitals?\n\nCore vitals are the most important metrics in Android vitals, and affect the\nvisibility of your app on Google Play. The core vitals are\n**user-perceived crash rate** , **user-perceived ANR rate** , and **excessive\npartial wake locks** for all apps, and **excessive battery usage** for watch\nface apps.\n\n#### What are the bad behavior thresholds?\n\nThe crash, ANR, and battery usage core vitals have two bad behavior thresholds:\none for all sessions across devices and one per device. These thresholds are\nshown in Android vitals.\n\n| BAD BEHAVIOR THRESHOLD To maximize your title's visibility on Google Play, please keep it under these thresholds. ||||\n| | Overall (average across devices) | Per phone model | Per watch model |\n|-------------------------------------|----------------------------------|-----------------|-----------------|\n| User-perceived crash rate | 1.09% | 8% | 4% |\n| User-perceived ANR rate | 0.47% | 8% | 5% |\n| Excessive battery usage | 1% | - | 1% |\n| Excessive partial wake locks (beta) | 5% | - | - |\n\nFor specifics on what partial wake lock use is considered excessive, see\n[Excessive partial wake locks (beta)](/topic/performance/vitals/excessive-wakelock).\n| **Note:** Tracking of excessive partial wake locks is **currently in beta**. The threshold numbers, relevant app states, and exceptions for behavior that has end-user benefit, are all subject to change. Once the metric is out of beta, excessive partial wake lock use may impact app visibility on Play.\n\n#### How do core vitals affect my title's visibility on Play?\n\nIf your app or game exceeds a bad behavior threshold, Play may reduce the\nvisibility of your title. Play may also show users a warning on your store\nlisting.\n\n#### Is it possible to have both per-device and overall bad behaviors? Or one but not the other? What do I do if so?\n\nYes, all combinations are possible. To improve app quality, fix the crashes and\nANRs affecting the most users. For better quality on specific devices, fix the\nbiggest crash and ANR groups on those devices. If you have both issues, focus\nfirst on the largest overall crash and ANR clusters.\n\n#### I need help to fix my technical issues. Where do I start?\n\nThe following resources resources are provided to help you diagnose and fix\ntechnical issues in your app or game.\n\n##### Core vitals:\n\n[User-perceived ANR rate](/topic/performance/vitals/anr#android-vitals) \n[User-perceived crash rate](/topic/performance/vitals/crash#android-vitals) \n\n[Excessive battery usage](/topic/performance/vitals/excessive-battery-usage) \n\n[Excessive partial wake locks (beta)](/topic/performance/vitals/excessive-wakelock) \n\n##### All other vitals:\n\n[Excessive wakeups](/topic/performance/vitals/wakeup) \n[Stuck partial wake locks](/topic/performance/vitals/wakelock) \n\n[Excessive background Wi-Fi scans](/topic/performance/vitals/bg-wifi) \n[Excessive background network\nusage](/topic/performance/vitals/bg-network-usage) \n[App startup time](/topic/performance/vitals/launch-time) \n[Slow rendering](/topic/performance/vitals/render) \n\n[Slow Sessions](/topic/performance/vitals/slow-session) \n[Low memory killers (LMKs)](/topic/performance/vitals/lmk) \n\n[Permission denials](/topic/performance/vitals/permissions) \n\n#### I don't want to be surprised by bad behaviors or store listing warnings. How can I get ahead of this?\n\nPlay uses the last 28 days of data to assess your app's quality. Android vitals\nwarn you about any problems during that period.\n\n- Regularly check the UI or use the reporting API to integrate data into your workflow.\n- Set up email alerts in the Play Console for issues.\n- Android vitals flags \"emerging issues\"---problems affecting devices for over 7 days. This gives you 21 days to address them.\n\n#### I have a lot of devices with bad behaviors. How do I make sense of the list?\n\nSometimes, device hardware or software problems cause high error rates. Android\nvitals alerts you to possible links between high error rates and things like\nRAM, Android version, and processor type. You can also investigate these links\nyourself using Reach and Devices in the Play Console.\n\nAndroid vitals also provides quick access to key device information, such as\nuser numbers, revenue, ratings, and reviews. This information is shown in a side\npanel, so you don't need to leave your current page.\n\n#### If I fix an issue on a device, how long before warnings stop showing?\n\nPlay checks your app's key performance indicators daily, using a 28-day average.\nWhen this average improves, Android vitals warnings disappear. Store listing\nwarnings may be removed faster if Play's system detects improvement.\n\n#### What if I can't fix the issue, or I don't want to do so?\n\nEnsure you've weighed the costs and lost opportunities from ongoing poor user\nexperiences. Bad behavior hurts current users and makes it harder to attract new\nones. If fixing problems on specific devices isn't practical, reconsider your\ndevice targeting and exclusion rules.\n\n#### Why don't Android vitals issue counts and rates match the issue counts and rates I see from my own or other third-party solutions?\n\nAndroid vitals is Play's main source for technical app quality. The number of\nissues and rates may differ from other sources for several reasons:\n\n- Android vitals data comes from the Android system and includes events not seen by SDKs, such as:\n - Crashes before SDK initialization\n - ANRs before Android 12\n- Android vitals only counts issues from certified devices and apps installed from Google Play.\n- Android vitals only uses data from users who agreed to share data.\n- To protect user privacy, we only show data if we have enough to make anonymous reports.\n- Issue rates may be calculated differently. Android vitals shows issues per daily active user.\n - For example, Crashlytics counts the number of issues per app session. If a user played a game three times in one day and experienced one crash, Android vitals would show a 100% crash rate while Crashlytics would show a 33% crash rate.\n\nFor more information on how data is collected, see the [Play Console Help\nCenter](https://support.google.com/googleplay/android-developer/answer/7385505).\n\n#### Can I see my ANR and crashes insights in the IDE?\n\nYes, from [Android Studio Meerkat](/studio), when viewing reports in App Quality Insights, click the Insights tab.\nGemini provides a summary of the crash, generates insights, and links to useful documentation. If\nyou also provide Gemini with access to local code context, Gemini can provide more accurate results,\nrelevant next steps, and code suggestions. This helps you reduce the time spent diagnosing and resolving issues.\nSee the [Android Studio documentation](/studio/debug/app-quality-insights) to learn more."]]
