Android Power Bug Analysis Skill

# Power Analysis Skill This skill is designed to analyze Android automotive power issues across AOSP and vendor layers. It is used when users mention specific power-related issues such as suspend, STR, resume, shutdown, power on, black screen, power policy, CPMS, CarPowerManagementService, PowerManagerService, PowerHal, PowerModing, displaypower, VHAL, gRPC, IPCL, garage mode, or vendor/ecarx power source code/logs. ## Key Capabilities - Analyze Android automotive power issues across AOSP and vendor layers. - Use when user mentions specific power-related issues. - Provide Jira single number, fault time, log path, source code path, or any combination of problem phenomena. - Recommend reading libraries for analysis. - Establish evidence chains between AOSP and Vendor Power main chains. - Provide module, class, and function-level anchors when source code is available. - Use a unified analysis framework for scenarios like sleep, wake, shutdown, power on slow, PowerPolicy, black screen, display联动, gRPC/IPCL disconnection, etc. - Output fixed-structure reports. ## When to Use - When users mention specific power-related issues. - When users provide Android Power-related logs. - When users provide AOSP directories, source code directories, or mention specific power-related components. - When users mention CPMS, CarPowerManagementService, PowerManagerService, PowerHal, PowerModing, DisplayPowerGrpcClient, AP_POWER_STATE_REQ, AP_POWER_STATE_REPORT. - In Jira scenarios where the problem phenomenon is obviously related to Android AP side Power or closely coupled with display联动. ## Example Use Case A user reports a black screen issue in their Android car. The skill can be used to analyze the issue by examining the relevant logs, source code, and other information provided by the user. ## Category Engineering ## Tags android, power-analysis, automotive, aosp, vendor, jira, logs, source-code