1. Headers
At the top level of the customer side, our products consume too much power and we need to solve the power consumption problem.
2. Ideas
First, determine whether the power consumption is required. The ZDbox software can be used to measure the power consumption of each application in the Android mobile phone.
Check the test results and compare different applications of the same type to determine whether the power consumption is significantly higher than that of others.
If the power consumption is significantly higher than that of others, first use SystemTunerPro to check what services are started in the background. Generally, the more background services, the larger the power consumption.
Carat can also be used to assess the power consumption structure and actively detect bugs.
3. Experience
Android's high power consumption is generally composed of the following four
A. Frequent GC, not necessarily full GC. If the full GC is frequent, the application will be very slow. Generally, the young gen GC is frequent.
B. Enable GPS, which especially consumes power.
C. network connection, especially when a bunch of services are opened in the background, the network connection is initiated every few minutes.
D. Number of backend services, opening a bunch of inexplicable services. One automatic update, one database update, and one nofication. And so on.
After my tests, apps in Japan usually consume a lot of power. The reason is that there are a bunch of services in the background, a dozen or so, and a network connection is initiated every 10 minutes. This is a typical style of Japanese products.
No one has taken the initiative, but it is outsourcing layer by layer. Everyone is working, and no one is willing to integrate the product architecture. It is useless to talk nonsense.
Author: nanjingjiangbiao