CN111385859A

CN111385859A - Terminal power consumption detection optimization method and device

Info

Publication number: CN111385859A
Application number: CN202010129228.6A
Authority: CN
Inventors: 高婉君
Original assignee: Beijing Jiuzhou Yundong Technology Co Ltd
Current assignee: Beijing Jiuzhou Yundong Technology Co Ltd
Priority date: 2020-02-28
Filing date: 2020-02-28
Publication date: 2020-07-07

Abstract

The embodiment of the invention relates to the technical field of electronic circuits, in particular to a method and a device for detecting and optimizing power consumption of a terminal. A terminal power consumption detection optimization method is applied to a terminal and comprises the following steps: determining a power consumption of the application; and optimizing the terminal according to the power consumption so as to save the power consumption of the application. The method of the invention optimizes the terminal to save power consumption by determining the power consumption applied on the terminal. So that the standby time of the terminal can be extended.

Description

Terminal power consumption detection optimization method and device

Technical Field

The embodiment of the invention relates to the technical field of electronic circuits, in particular to a method and a device for detecting and optimizing power consumption of a terminal.

Background

Mobile terminals have become widely popular; the power consumption of the mobile terminal is generally detected by using an android power consumption test experiment; in the prior art, a terminal is provided with a plurality of application apps; the power consumption of the terminal can be detected by existing detection software or hardware, but no further optimization measures can be taken to reduce the power consumption of the terminal.

Disclosure of Invention

Therefore, the embodiment of the invention provides a method and a device for detecting and optimizing power consumption of a terminal, so as to save the power consumption of the terminal.

In order to achieve the above object, the embodiments of the present invention provide the following technical solutions:

according to a first aspect of an embodiment of the present invention, a method for detecting and optimizing power consumption of a terminal, applied to the terminal, includes:

determining a power consumption of the application;

and optimizing the terminal according to the power consumption so as to save the power consumption of the application.

Further, optimizing the terminal includes: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

Further, optimizing the locking mechanism in the terminal includes:

removing redundant wake locks in the application.

Further, optimizing a Central Processing Unit (CPU) in the terminal comprises the following steps:

determining services which do not need to be operated in the CPU;

and closing the service which does not need to be operated.

Further, optimizing the network environment in the terminal includes one or more of the following:

optimizing the retry times of the terminal connecting with the network, presetting the preset network connection retry times, and when the retry times of the terminal connecting with the network reach the preset threshold value, the terminal does not retry to connect with the network;

optimizing a scene of big data transmission, comprising: when the terminal is in a wifi connection scene, a big data request is carried out, and when the terminal is in a non-wifi scene, big data transmission is not carried out;

the big data refers to data with the size of data volume exceeding a preset value;

setting a cache for the application; when the application starts, the start item is stored in the cache.

According to a second aspect of the embodiments of the present invention, a device for detecting and optimizing power consumption of a terminal, applied to the terminal, includes:

an application power consumption determination module for determining power consumption of an application;

and the optimization processing module is used for optimizing the terminal according to the power consumption so as to save the power consumption of the application.

The optimization processing module is further configured to: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

Further, the optimization processing module is further configured to: removing redundant wake locks in the application.

Further, the optimization processing module is further configured to: determining services which do not need to be operated in the CPU;

and closing the service which does not need to be operated.

Further, the optimization processing module is further configured to:

The embodiment of the invention has the following advantages: according to the invention, the power consumption of the terminal is determined, and the terminal is optimized according to the power consumption, so that the power consumption of the terminal is reduced, and the standby time of the terminal is prolonged.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.

The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so that those skilled in the art can understand and read the present invention, and do not limit the conditions for implementing the present invention, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the functions and purposes of the present invention, should still fall within the scope of the present invention.

Fig. 1 is a flowchart of a method for optimizing power consumption detection of a terminal according to an embodiment of the present invention;

fig. 2 is a schematic interface diagram of historian according to an embodiment of the present invention;

fig. 3 is a schematic interface diagram of another historian according to an embodiment of the present invention;

fig. 4 is a schematic interface diagram of another historian according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a device for detecting and optimizing power consumption of a terminal according to an embodiment of the present invention.

Detailed Description

The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The invention provides a method for detecting and optimizing power consumption of a terminal, which is applied to the terminal and comprises the following steps of:

step S101, determining the power consumption of the application;

the method comprises the following steps of acquiring power consumption data of a terminal by adopting the following method;

the current electricity measuring equipment in common use includes: agilent electrometer, Battery historian, Power Tutor, and Energy Profile.

Wherein, Agilent electricity tester: mechanical equipment capable of directly providing current for the mobile phone.

Battery historian: a battery power consumption detail tool for analyzing a mobile phone APP by uploading a system power consumption file.

Power turbine: the university of michigan, usa, developed under the guidance of google, respectively establishes power consumption models for devices such as CPU, WIFI, LCD, 3G, GPS and AUDIO, and performs power consumption calculation statistics.

Energy Profile: a model is used to estimate the energy consumption (network radio, GPS sensor usage, system events, etc.) of each resource on the device.

Wherein, mAh: refers to units of battery capacity; the battery capacity refers to the amount of electricity stored in the battery, the unit of the battery capacity is mAh/Ah, the Chinese name is mAh/Ah (1Ah is 1000mAh), the rated capacity of the battery is 1300mAh (if the battery is discharged by 130mA of current, the battery can last for 10 hours, 1300mA/130mA is 10h)

Among them, in one embodiment, Battery historian is preferably used.

The applicant finds out through experiments that the technical scheme of Batery historian is optimal.

The experimental protocol was as follows: market app (hundredth sdk), a network positioning mode, 10-minute operation and Wi-Fi environment, wherein the 4 types of software are respectively used for measuring, counting the power consumption of the equipment and converting the power consumption into a unified unit for comparison. See table 1 for a comparison of results of the four charge monitoring techniques.

Testing equipment: three stars S4

TABLE 1

And S102, optimizing the terminal according to the power consumption so as to save the power consumption of the application.

Wherein, optimize the terminal, including: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

The method of the invention is realized by determining the power consumption of the application; and optimizing the terminal according to the power consumption so as to save the power consumption of the application and save the electric energy of the terminal.

In one embodiment, optimizing a lock mechanism in a terminal includes:

removing redundant wake locks in the application.

The wake-up lock is a tool set for waking up the CPU and avoiding the system from sleeping; for example, a heartbeat packet with a WeChat communication in time may stop network access shortly after the screen is turned off. The WeChat is provided with a large number of wake _ lock locks. Wake-up locks may not be used overly frequently; if used frequently, this increases power consumption.

Review code, retrieve all wake locks, remove redundant or useless wake locks.

2. By implementing or optimizing the algorithm in the prior art, as is well known, the wakeup task is calculated by a jobscheduler API to control the timing of the wakeup task, and the scheduling algorithm can be optimized by considering the jobscheduler API.

In one embodiment, optimizing a central processing unit CPU in a terminal includes:

removing redundant services and determining services which do not need to be operated in the CPU; and closing the service which does not need to be operated. Avoiding long-time execution of power consumption operation;

code computation minimizes floating point operations.

In one embodiment, the network environment in the terminal is optimized, and the network environment comprises one or more of the following:

in the network abnormal scene, the network retry times are limited, and the frequent triggering request of the network abnormality is avoided; the retry times of the terminal connecting with the network can be optimized, the preset network connection retry times are preset, and when the retry times of the terminal connecting with the network reach the preset threshold value, the terminal does not retry to connect with the network;

the data request time is optimized, and a large amount of data is prevented from being triggered at the same time;

distinguishing the number of times of triggering requests of a network environment, and controlling the requests in a Wi-Fi scene as much as possible when the requests of large data are large;

the big data refers to data with the size of data volume exceeding a preset value; the predetermined value can be flexibly set, and the application is not limited. For example, if the size of a data packet to be uploaded by the terminal exceeds 500M, the terminal determines to transmit the data packet in a wifi connection scene; and if the terminal is not connected with wifi currently, the data packet is not transmitted. Thus, power consumption of the terminal can be reduced.

In one embodiment, the data analysis selects an efficient analysis tool, and an analysis tool algorithm is optimized; selecting a json protocol by the Android;

in one embodiment, a cache may also be set for the application; when the application starts, the start item is stored in the cache. The method is mainly applied to the scene of games, and when a game interface is accessed, resources are often required to be loaded. If a cache is provided, the resource may be stored in the cache. Network requests are avoided each time a game is started. The electric energy is saved.

In one embodiment, the front-end and back-end communication framework rationalizes avoiding the situation of round robin requests.

The method of using Battery historian is described as follows:

the use method I comprises the following steps:

1. downloading Batery historian https:// github. com/google/Batery-historian;

2. decompress and place historian.

3. Linking a computer with the equipment;

4. opening a command terminal;

5. to the catalog of historian. $ cd-/Android/butterystats;

6. stopping adb server: $ adb kill-server;

7. device viewing the link: $ adb devices;

8. the terminal operates an intercepting electric quantity command and clears original data:

$adb shell dumpsys batterystats–reset；

9. closing the non-test application, disconnecting the power supply link and opening the test application;

10. operating a running test application specific scenario;

11. end of scene, relink device (ensure test device is visible through $ adb devices)

12. Outputting the electric quantity data to a text file:

$adb shell dumpsys batterystats>～/Android/batterystats/batterystats.txt；

13. generating html from the electric quantity data file battrystats.txt, and opening the battrystats.html file by using the browser;

$python historian.py batterystats.txt>batterystats.html。

the use method II comprises the following steps:

1. downloading a GO installation file for installation, and confirming successful installation of GO version;

2. configuring an environment variable of Go;

the environment variable configuration file is written as follows:

I.export GOPATH＝$HOME/work；

Ii.export GOBIN＝$GOPATH/bin；

Iii.export PATH＝$PATH:$GOBIN；

2. the terminal executes the command and downloads the Battery-Historian source code;

Go get-d-u github.com/google/battery-historian/～

4. the terminal operates Battery Historian;

5. visit localhost: 9999, opening a battery historian analysis interface;

6. the terminal operates an intercepting electric quantity command and clears original data:

$adb shell dumpsys batterystats–reset；

7. disconnecting the computer, operating the specific scene of the app application, and re-linking the mobile phone after the specific scene is finished;

8. acquiring a button by terminal input: $ adb budget > budget

And 9. uploading bugspot.

Battery Historian can convert all the acquired electricity consumption values into a chart form, see fig. 2 and 3; the states and power consumption conditions of various hardware and software of the mobile phone, including the running of a CPU, whether a screen is started, WiFi signal strength, a charging state, an electric quantity consumption curve and the like, can be checked in the chart.

The obtained APP with the most power consumption at any moment is obtained by calculating the power consumption at the moment through a tool, and the power consumption is not very accurate, for example, in the same operation scene for many times, when the power consumption changes, the APP with the most power consumption can display larger power consumption;

conventional analysis procedure:

1. the chart is analyzed integrally, the integral trend of app power consumption is checked, and a top module for confirming power consumption is checked;

2. selecting an application, clicking a chart to check detailed chart data information, and specifically analyzing a test object;

3. the problem troubleshooting can be combined with the output of the exported files batterytats;

referring to fig. 3, in which,

bettery _ level is the right-side electric quantity coordinate; the black line indicates the change in power;

cpu _ running: cpu run time;

screen: whether the screen is lighted or not (the information can be used for confirming that the power consumption condition of the LED screen of the equipment is approximately equal to the power consumption of the screen-the power consumption in the sleep state);

WiFi _ running: WiFi links active time (disconnected & networked power consumption information, where one can focus on);

GPS: GPS runtime, GPS state can be turned on or off in the device settings;

foreground process: running background process information;

plugged: current device charging status (this information shows whether the current device is in charging status, and the effective time of charging);

wakelock (a locking mechanism): app start-run-sleep, as described above in fig. 1, the start power consumption is unstable due to intensive fluctuations in the start range, which may be an abnormal phenomenon;

analysis of the Batery Historian table referring to FIG. 4, the Batery Historian table includes: system states, history states, and app states;

wherein the system state includes: the module time length, the power consumption ratio of each module, wakelock times and the like correspond to the detailed label data.

The application states include: the application name, the version number, the equipment power utilization estimation, the CPU use time and the wakeup alarm times.

Based on the same inventive concept, the application also provides a terminal power consumption detection optimization device, which is applied to a terminal and refers to the structural schematic diagram of the terminal power consumption detection optimization device shown in the attached figure 5; the method comprises the following steps:

an application power consumption amount determination module 51 for determining power consumption amount of an application;

and the optimization processing module 52 is configured to optimize the terminal according to the power consumption to save the power consumption of the application.

In one embodiment, the optimization module 52 is further configured to: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

In one embodiment, the optimization module 52 is further configured to: removing redundant wake locks in the application.

In one embodiment, the optimization module 52 is further configured to: determining services which do not need to be operated in the CPU;

and closing the service which does not need to be operated.

In one embodiment, the optimization module 52 is further configured to:

Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.

Claims

1. A method for detecting and optimizing power consumption of a terminal is applied to the terminal and comprises the following steps:

determining a power consumption of the application;

2. The method for optimizing power consumption detection of a terminal as claimed in claim 1, wherein the optimizing the terminal comprises: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

3. The method for optimizing power consumption detection of a terminal as claimed in claim 2, wherein optimizing the lock mechanism in the terminal comprises:

removing redundant wake locks in the application.

4. The method for optimizing power consumption detection of a terminal according to claim 2, wherein optimizing a central processing unit CPU in the terminal comprises:

determining services which do not need to be operated in the CPU;

and closing the service which does not need to be operated.

5. The method for optimizing power consumption detection of a terminal according to claim 2, wherein the network environment in the terminal is optimized, and the method includes one or more of the following:

6. The utility model provides a terminal power consumption detects optimizing apparatus which characterized in that, is applied to the terminal, includes:

7. The apparatus for optimizing power consumption detection of a terminal according to claim 6, wherein the optimization processing module is further configured to: and optimizing the locking mechanism of the application, a Central Processing Unit (CPU) of the terminal and the network environment of the terminal.

8. The apparatus for optimizing power consumption detection of a terminal according to claim 7, wherein the optimization processing module is further configured to: removing redundant wake locks in the application.

9. The apparatus for optimizing power consumption detection of a terminal according to claim 7, wherein the optimization processing module is further configured to: determining services which do not need to be operated in the CPU;

and closing the service which does not need to be operated.

10. The apparatus for optimizing power consumption detection of a terminal according to claim 7, wherein the optimization processing module is further configured to: