耗电量过高
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
耗电量过高是指每小时耗电量超过 4.44% 的表盘工作时段所占百分比。Google Play 会在设备未在充电且未运行任何应用时收集此类数据。
如果每小时电池用量超过 4.44%,手表将无法单次充电续航一整天。这会给用户和 Wear OS 生态系统造成伤害。
如需最大限度地延长电池续航时间,请将每小时电池用量控制在 3.2% 以下。
效率要求
高效的表盘应用应具有以下特点:
- 耗电量过多(小于 1%)
- 80% 的工作时段每小时电池用量 < 3.2%
重要指标会提供以下数据:
- 电池用量随着时间的推移而过高
- 每小时电池用量直方图
- 影响因素
- 细分
影响因素
以下是影响应用耗电量的关键因素:
- CPU 使用率过高:每小时使用 CPU 时长至少为 90 秒的表盘工作时段所占的百分比。
- 部分唤醒锁过多:表盘会话中有一部分每小时使用唤醒锁定 18.5 秒或更长时间。
您可以使用细分和 Battery Historian 进行进一步调查。
细分
细分会按操作系统、设备和地区等特征对受影响的会话进行分组。选择一个细分,查看该组的每小时电池用量直方图。
降低电池用量
请参考以下建议来减少应用的电池用量。
使用表盘格式
表盘格式使用声明式 XML(而非可执行代码)来简化应用创建流程并减少电池用量。
处理屏幕常亮 (AoD) 模式
当手表处于闲置状态时,它会切换到“屏幕常亮”(AoD),也称为“氛围模式”。在 AoD 模式下,表盘点亮的像素不应超过 15%。
优化内存使用情况
大图片、大字体和动画(例如秒针摆动)会增加电池用量。
- 使用所需的最低分辨率资源
- 将资源剪裁为最小尺寸(避免透明边框)
- 移除或剪裁被其他元素遮盖的所有内容,以减少过度绘制
如需更多建议,请参阅优化内存用量。
限制动画
为元素添加动画会让表盘主题看起来更具吸引力,但会增加耗电量。
为减少这些影响,请执行以下操作:
- 避免使用高帧速率动画
- 限制使用 Gyro 和 ArithmeticExpression 等动态元素
ArithmeticExpression
的更新频率与其来源数据相同。MILLISECOND
和 ACCELEROMETER
等高频源会耗用更多电池电量。
- 避免在 AoD 模式下显示不必要的动画
避免使用唤醒锁
使用表盘格式发布应用,以避免唤醒锁。
为您推荐
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Excessive battery usage\n\n| **Note:** Excessive battery usage is only available for watch face apps with sufficient usage data.\n\nExcessive battery usage is the percentage of watch face sessions where battery\nusage exceeds 4.44% per hour. Google Play collects this data when devices aren't\ncharging and no apps are in use.\n\nWhen battery usage exceeds 4.44% per hour the watch won't last a full day on a\nsingle charge. This harms users and the Wear OS ecosystem.\n\nTo maximize battery life, aim for battery usage under 3.2% per hour.\n\nEfficiency requirements\n-----------------------\n\nAn efficient watch face app should have:\n\n- \\\u003c 1% excessive battery usage\n- \\\u003c 3.2% battery usage per hour for 80% of sessions\n\n| **Warning:** If excessive battery usage exceeds 1%, Play may reduce your app's visibility. See [core vitals FAQ](/topic/performance/vitals#core-vitals-faqs) for more details.\n\n[Vitals](/topic/performance/vitals) provides the following data:\n\n- Excessive battery usage over time\n- Battery usage per hour histogram\n- Contributing factors\n- Breakdowns\n\nContributing factors\n--------------------\n\nThese are key factors affecting your app's battery usage:\n\n- **Excessive CPU usage:** The portion of watch face sessions that use the CPU for 90 seconds or more per hour.\n- **Excessive partial wakelocks:** The portion of watch face sessions use wakelocks for 18.5 seconds or more per hour.\n\nUse [breakdowns](#breakdowns) and [Battery Historian](/topic/performance/power/battery-historian) to investigate further.\n\nBreakdowns\n----------\n\nBreakdowns group affected sessions by characteristics such as OS, device, and\nregion. Select a breakdown to see an hourly battery usage histogram for that\ngroup.\n\nReduce battery usage\n--------------------\n\nUse the following suggestions to reduce your app's battery usage.\n\n### Use Watch Face Format\n\n[Watch Face Format](/training/wearables/wff) uses declarative XML instead of executable code to\nsimplify app creation and reduces battery usage.\n\n### Handle Always on display (AoD) mode\n\nWhen a watch isn't in use it switches to Always-on display (AoD), also called\nambient mode. In AoD, your watch face should [illuminate no more than 15% of\npixels](/docs/quality-guidelines/wear-app-quality#always-on-display).\n\n### Optimize memory usage\n\nLarge images, fonts, and animations (like sweeping second hands) increase\nbattery usage.\n\n- Use the lowest resolution resources needed\n- Crop resources to their minimum size (avoid transparent borders)\n- Remove or crop anything hidden by other elements to reduce overdraw\n\n| **Tip:** Use the [Watch Face Format Optimizer](https://github.com/google/watchface/tree/main/tools/wff-optimizer) to automatically apply some optimizations.\n\nSee [Optimize memory usage](/training/wearables/wff/memory-usage) for more suggestions.\n\n### Limit animations\n\nAnimating elements makes watch faces visually appealing but uses more battery.\nTo reduce their impact:\n\n- Avoid using high fps animations\n - For most animations 15 fps is recommended\n- Limit usage of dynamic elements such as [Gyro](/training/wearables/wff/common/transform/gyro) and [ArithmeticExpression](/training/wearables/wff/common/attributes/arithmetic-expression)\n - `ArithmeticExpression` updates as frequently as its source data. High frequency sources such as `MILLISECOND` and `ACCELEROMETER` use more battery.\n- Avoid unnecessary animations in AoD mode\n\n### Avoid wakelocks\n\nPublish your app using [Watch Face Format](/training/wearables/wff) to avoid wakelocks.\n\nRecommended for you\n-------------------\n\n- Note: link text is displayed when JavaScript is off\n- [Watch Face Format](/training/wearables/wff)\n- [Power considerations](/design/ui/wear/guides/surfaces/watch-faces#power_considerations)\n- [Battery Historian](/topic/performance/power/battery-historian)"]]