In this paper, combined with the document, a simple summary of the AP power consumption analysis methods.
The first is the official power consumption analysis flow chart
Pay attention to several key terms:
RPM resource power manager is an additional chip added to the Qualcomm MSM platform to control the whole power related shared resources
APSS application processor subsystem is what we usually call AP
The problem of power consumption is generally divided into low current, high current, or abnormal wake-up.
This paper only analyzes the power consumption from the perspective of AP, that is, from the perspective of Android system.
If the low current is too high, it is necessary to verify whether the system has entered the minimum power consumption state. VDD minimum state.
mount -t debugfs none /sys/kernel/debug/
If the system does not enter the VDD minimum state, check which item prevents the terminal from entering the VDD minimum state.
This section mainly looks at the external log of RPM. Analysis, omitted.
Next, analyze the power consumption problem caused by abnormal wake-up
Check the abnormal wake-up source of the AP side and check the skip of the modem block.
echo 1 >/sys/module/msm_show_resume_irq/parameters/debug_mask echo "8 8 8 8">/proc/sys/kernel/printk
By viewing the status of the wake-up lock, you can mainly view active_ In the since field, you can see which lock caused the system to fail to sleep.
Conclusion: the power consumption problem of AP terminal is generally judged from low current state.
Troubleshooting: remove some external drivers, such as sensor, TP, camera, LCD, etc.
cat /sys/kernel/debug/rpm_ Stats gets whether the system is sleeping. Verify XO shutdown and VDD minimization
Check the log to get the abnormal wake-up source
echo "8 8 8 8">/proc/sys/kernel/printk